As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
yep, thanks, maybe that was the problem, maybe I had associated a wrong profile, or maybe it was just a cluster of different problems... I'm not sure which one was actually.
While trying to solve I basically went again through the whole process of registering my device, creating certificates, and so on... and also changed some build settings on XCode, in Code Signing section, also about provisioning... and it ended up working :)
M
Mike
said
almost 10 years ago
Did you build with the associated provisioning profile?
Davide Neri
I followed the guide (http://devcenter.kinvey.com/ios/guides/push) , or at least I think I did...
I basically:
- created the App ID,
- enabled push,
- created the certificate,
- p12 for development,
- uploaded the p12 on Kinvey,
- copy-pasted the code from the guide to my app,
- placed the registerForPush in loginWithUsername success function
....but but in the end isn't working.
When I call [KCSPush registerForPush] the app goes to didFailToRegisterForRemoteNotificationsWithError and throws this error:
"NSCocoaErrorDomain" - code: 3000
"NSLocalizedDescription" : @"no valid 'aps-environment' entitlement string found for application"
What could the problem be?
Thanks!