I tried to catch and cover all the questions you had.

Thanks for your help.
But I still do not understand how to deploy the new entitlements file

The original file, that I am supposed to Uncheck, is named "IOSDevice\Debug\ApplePushRemote.Entitlements" with the
remote name of "Entitlements.plist".

This file does not exist in the source code from Luis, and I guess it will be generated the first time you compile the project.

His file is called "Prueba.entitlements", and I guess this is the file that I am supposed to make a copy of and load in to the deployment window.
Will this new file then become ApplePushRemote.Entitlements the first time I compile?
If so; Why do I need to UnCheck the "AppPushRemote.Entitlements" in the first place?
If not; Where is the link between Prueba and AppPushRemote.Entitlements? I can’t find any settings or properties which indicate those two files are the same.

(I have even had someone to translate his video for me, but it didn’t help..)

Anders has been trying to help. This AM, I managed to get the app to register for APNS. But, it’s still not receiving my messages (I know my sender works).

I did see that the CFBundleName and CFBundleIdentifer had to be set in the demo. And, it looks like the aps-environmentdevelopment needs to also be set.

What isn’t clear is whether the application-identifieryour app id also needs to be set. I suspect it does.

Make sure you don’t have CRLF’s in your entitlement file.

In Deploy, you need to uncheck the .Entitlements entry and then supply your own with a file of a different name. The remote does need to Entitlements.plist, though.

I would suggest editing the Entitlements file on your mac and copying it back to be sure it’s in the right format.

That’s as far as I have gotten.

Can you please explain "In the Deployment tab - uncheck the old one. Deploy the new one to Entitlements.plist." more detailed?

Do you mean; add the file xxx.entitlements and then change the value of the "Remote name"-field to Entitlements.plist?

It would have been great if you also could post which other changes we have to make before this demo will work. As I understand it, I will also have to change the values in Project->Options->Version info?

Can you briefly share how to handle single-tap and double-tap of the iOS device screen? Double-tap is not a problem - the GestureManager allows for it. However, I am forced to use Click or MouseDown event handler as a single-tap handler. But the problem is that the MouseDown and Click events also get fired when a double-tap event occurs. Is there anyway to handle these events without any logic conflicts?

Jed does bring up some good points regarding native controls - As you know…my pet peeve is Push Notifications (still can’t get the example posted in your other entry to work).

I would love to see (in order) in the next update:
1. Ability to use our own provisioning profiles during development.
2. Push Notifications code (vs a hack) out of the box that works.
3. Documentation showing HOW and when to call native iOS functions.
4. More complete native control wrappers (and exposing more capabilities of existing ones).
5. Android and/or Windows 8 Store support.

There…my wish list.

I am, however, very pleased with this latest release despite the changes in the language (one String type is taking some time to get used to…but, I understand WHY it was done).

Now…I need to get back to a company that is, on their job posting, listing and, I quote, "Older Programmer Languages - Delphi"). We need to break that perception!