Developer Portal should offer provisioning profile update after adding new app service
| Originator: | nskboy | ||
| Number: | rdar://15457600 | Date Originated: | 13-Nov-2013 03:51 PM |
| Status: | Open | Resolved: | |
| Product: | Developer Tools | Product Version: | Current |
| Classification: | Other Bug | Reproducible: | Always |
Summary: Consider an app that was published in App Store without push notifications. The next update adds push notifications support and a typical scenario looks as follows: edit app to enable push notifications, generate APNS server certificates and there is no step 3. But this change breaks provisioning profile of this app. Upon uploading app built with this profile you receive a warning "Your app appears to include API used to register with the Apple Push Notification service, but the app signature's entitlements do not include the 'aps-environment' entitlement". That's frustrating. It would save a lot of time if developer portal offered to update provisioning profile immediately after enabling push notification service. Steps to Reproduce: 1. Release an app to App Store without push notifications enabled 2. Enable push notifications for this app 3. Generate APNS server certificates 4. Attempt to upload an app built with outdated provisioning profile Expected Results: iOS Developer Portal should offer provisioning profile update immediately after enabling push notifications service. Actual Results: iOS Developer Portal doesn't offer provisioning profile update Version: Current iOS Developer Portal version Notes: Configuration: Attachments:
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!