OK, So I deleted everything and started over. What I noticed is that the Certificate Generation had a team ID that did not match the one that I use normally (don't know where it comes from or why) so I changed to the ID that I normally use and this time instead of following the Lesson I used John's "Apple Push Notification Server Assistant" to build out the certs and PEMs and then created a new App ID and generated the new certificate. Finally I created a new provisioning profile and and new build and now the device will 'take' the Livecode app built with this new provisioning profile.
All seems good until I try to type in the device token reported back from my device into the APNS Assistant. I keep getting an error at line 28 stating the binaryEncode: invalid data for parameter near: "xxxxx my token number xxxx" Has anyone run into problems with that before???? Thanks Tom -- Tom McGrath III http://lazyriver.on-rev.com [email protected] On Apr 16, 2013, at 3:04 PM, Thomas McGrath III <[email protected]> wrote: > 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? > > 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 > [email protected] > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
