Post not yet marked as solved
Didn’t they deprecate this method for APNS?
Now token based
Post marked as Apple Recommended
Disabling Bitcode sadly is not a fix if you have a WatchOS app
Post not yet marked as solved
Yes I am also seeing this now with the 13.3 release.
We also cannot disable BitCode due to a WatchOS app
Post not yet marked as solved
Now this is live is there any tech guides on how this is implemented?
Specifically around the identifications, is there any links back to the original purchase ID at all?
Post not yet marked as solved
To clarify,
Ideally we would like each user linked to a Family Sharing transaction to have their own original_transaction_id and susbsequent renewal transactions of their own.
The original Apple recommendations said to rely on this field and so a lot of code hinges around this being unique to a subscription (and with relevant usage limits applied in our code too).
If these get treated as “new” users essentially we are happy for that but ideally some sort of flag saying they are linked to an original in case people run local billing metrics!
Post not yet marked as solved
Sorry, my reply was being written as you sent that.
Will each Apple ID have a unique original_transaction_id or will it be the same as the primary user?
Post not yet marked as solved
Apple send back the Key Id "kid" in the response so you can lookup the appropriate key
Post not yet marked as solved
I have raised a case with Apple Developer Program Support.They didn't have any insight and wanted screenshots etc which I have sent over
Post not yet marked as solved
Sadly not, no. I have asked for a few updates and not had a response.I checked Friday and I was still not seeing it in the sandbox too.
Post not yet marked as solved
I filed a feedback back in December for this as saw the same..FB7467964
We get the same issue since iOS13.1 on iPads only.https://forums.developer.apple.com/thread/122064Have you raised a Radar as well? It's the only way really to get some traction and them to look at the issue!
For now we have worked around it on iOS 11 but it has meant a ton of extra code.Hopefully it will be fixed but hopefully you've raised a Radar yourself?
Post not yet marked as solved
Again we need some way of determining an iPad
Post not yet marked as solved
Yes a few are getting this. I managed to recreate in a sample project and raised a radar with Apple. No response yet. FB7144402
