Posts

Post not yet marked as solved
1 Replies
950 Views
Hello, I've run across the iOS Distribution Managed Certificate a few times in our enterprise account, but I've never been able to find concrete documentation or wwdc videos relating to how to actually build an enterprise app using cloud certificates (which as far as I can tell is the iOS Distribution Managed certificate that mysteriously appeared in many people's enterprise accounts a few years ago). Background: our normal enterprise cert is expiring this week and unfortunately, a separate team in the organization generated a 2nd cert already for their app, so we are unable to generate a cert early to overlap the expiration time and avoid downtime. We are attempting to work with them, but logistical challenges might cause us to miss the expiration date - cloud cert would be a great solve here if possible. Any resources would be greatly appreciated! I have found this page, but the details are very limited and it seems tat there is some specific detail that is left out since it says the organizer will simply sign with cloud certificate automatically - perhaps a local cert purge is required to get this to work? https://developer.apple.com/help/account/create-certificates/cloud-managed-certificates/
Posted
by mharlow.
Last updated
.
Post not yet marked as solved
2 Replies
2.4k Views
I am testing my production app on iOS 13 Beta 7 devices and also my development version on the same devices via XCode11 Beta 5 - I am noticing that "silent" push notifications (notifications without message, badge, or sound) are not being received by my apps. If I test notifications with a message, badge, or sound, the notification comes through fine, but not the silent variety (the purpose is to help the app refresh it's data based on backend data-update).For reference, background notifications are not necessarily involved here, I am seeing these issues in the foreground. As you would assume, the identical implementation works fine on iOS 12 devices and Xcode 10 built apps.I use Pushy as the middle-man for push notifications. In their API terminology, the pushes look like this (below). I can dive in and determine exactly what the APNS payloads are that are being sent if it would help.Any direction on if "silent" notifications are being changed in 13, if a better solution for silent notifications exists, or if there are known bugs in the betas would be great to hear!-------"Silent" Notification (not received by iOS 13 devices):{ "to":"[pushy token (different from APNS token but 1:1]", "data": { // this is the custom data section - not mapped to the typical message-body of an Apple Push Notification "Message": { "customDataKey": "customDataValue" } }, "content_available": true, "time_to_live": 604800}Normal Notification (working fine):{ "to":"[pushy token (different from APNS token but 1:1]", "data": { "Message": { "customDataKey": "customDataValue" } }, "notification": { "body": "standard apple notification body" }, "content_available": true, "time_to_live": 604800}
Posted
by mharlow.
Last updated
.