If you have an opportunity to join our webinar this coming weekend no Sunday March 30th at 10:00AM Central Standard Time, I would highly recommend it.  We will be addressing this very issue.  I have not made a decision on whether I will be recording this webinar.

Click here to register for the webinar.

Share your app with interactbuilder@gmail.com and we will see if it crashes over here.  Let us know once you share it.

So Ranco, are you all set now?  Or do you still need us to upload a corrected version of your example?  Let us know.

Actually this is not a bug. The problem is that you are using a global element which has an action set on it to update itself on page load. This means that every page will essentially reset the value of this counter.  

To resolve this issue simply update the counter on page refresh from another element and this should resolve the problem.  If you need more information or a better explanation please let us know.

We are still evaluating our entries.

We received it. Thanks Clint.

Adeel, 

We tested just now on a Nexus 5 that had a previous version of Urdu,  and it worked without a glitch.  Maybe try uninstalling the app from your Droid, that shouldn't be necessary but that is the only idea we have.  We are going to try it on a couple of other devices to see if there is still an issue.

Adeel, we did find an issue with the upgrade process. We are working to fix this ASAP!

Adeel, 

We tested just now on a Nexus 5 that had a previous version of Urdu,  and it worked without a glitch.  Maybe try uninstalling the app from your Droid, that shouldn't be necessary but that is the only idea we have.  We are going to try it on a couple of other devices to see if there is still an issue.

By definition a chained behavior occurs after the first behavior.  If you still need a delay then add a delay before the second action set or after the first one, but regardless try using chained behavior.