Thomas,

Please see below how to solve this smoothly :

Le 16 avr. 2013 à 21:04, Thomas McGrath III a écrit :

> Hello all,
> 
> I am trying to build a sample app for testing my push notification server.
> I am following the lesson at: 
> http://lessons.runrev.com/s/lessons/m/4069/l/53405-how-do-i-use-push-notifications-with-ios
> 
> Even though that lesson is out dated I was able to:
> Create a Development Certificate for this push app: In the Developer Portal 
> it states the name as "com.lrs.SkinDeepTattooGallery" and type as "APNs 
> Development iOS"
> Create an App ID: In the Portal it states Name as "SkinDeepTattooGallery" and 
> ID as "com.lrs.SkinDeepTattooGallery"
> Create a Provisioning Profile: In the Portal it states Name as 
> "SkinDeepTattooGallery" and type as development and status as "Active"
> 
> But when I assign this profile in a standalone and then try to drop it on my 
> device in the xCode Organizer I get the error: "The executable was signed 
> with invalid entitlements. The entitlements specified in your application's 
> Code Signing Entitlements file do not match those specified in your 
> provisioning profile."
> 
> So I go back to the Provisioning Portal and select the Development 
> Provisioning Profile and it only lists my normal "iOS Development: Thomas 
> McGrath II (iOS Development)" in the list of Certificates when I edit the 
> SkinDeepTattooGallery Profile. It does not list the Certificate created 
> earlier in the Developer Portal. So I go and check and the 
> com.lrs.SkinDeepTattooGallery as type "APNs Development" is still there as a 
> valid certificate BUT it does not show up as a choice in the Provisioning 
> Profile. So I can not build an app in Livecode because it will be invalid.
> 
> I was under the impression from the Lesson that each app had to have a "NEW" 
> certificate, unique App ID and Provisioning Profile for Push Notification. 
> Yet the new certificate does not show up in Apple's Provisioning Profile for 
> my profile BUT my regular Certificate does show up.
> 
> Has anyone run into this and know how to correct for this?

Take care to verify that you have authorized your test devices to receive both 
the normal iOS dev profile (Xcode does this for you). and the Push one in the 
Apple Provisioning Portal (select the Push dev profile and edit it to get the 
next window appears and let you select the devices you want the Push dev 
profile to be installed on). That done, go back to Xcode and click on the 
refresh button of the Provisioning Profiles tab to get the need Push 
provisioning profile installed on the previously selected (on the Apple dev 
portal side) test devices.

Best,

Pierre
> 
> Is it possible to use my existing regular 'for Development' Certificate that 
> is listed and just edit that for use with Push or do I truly need a unique 
> one as the lesson states?
> 
> If so is there a step I missed or how do I get the 'Push' Certificate to show 
> up in the list of available certificates in that Profile?
> 
> Thanks to all who can help.
> 
> Tom
> 
> 
> -- Tom McGrath III
> http://lazyriver.on-rev.com
> mcgra...@mac.com
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

--
Pierre Sahores
mobile : 06 03 95 77 70
www.sahores-conseil.com


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to