SwiftyStoreKit: iOS 16 (am not sure) restoring purchases hangs?
Restoring purchases hangs
I am not sure if this is AppStore issue, but today I cannot successfully call restoring purchases method. Completion handler is never called - hangs. Anyone else with this issue?
My third app still built with Xcode 13 is ok. Both my other apps built with Xcode 14 have the same issues - hangs. I guess the problem could not be with Bitcode setting No (it is not recommended anymore having Bitcode Yes on Pods)?
EDIT: More specifically, this one hangs restoreCompletedTransactions
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 10
- Comments: 45 (1 by maintainers)
I think Apple fixed this bug in iOS 16.0.3 .
I have confirmed that it works with Xcode 14.1 RC2, iOS 16.1 and a combination of TestFlight and SwiftyStoreKit, and my app was able to restore.
I would appreciate it if you could also check if you are having this issue.
Guys I finally migrated to StoreKit2 and it was more easy than expected. Also I had important issues with Testflight versions and the damn sandbox server. So I finally figure out that after doing a phone reset and using a single apple id (don’t ever change it if you can) everything worked as expected. Hope it helps
FYI, it’s also in Production environment. As recommended, I have refactored first of my apps to StoreKit2 with the help of Mercato git library.
I can confirm that this is happening on iOS 16 even when build with Xcode 13.
I refactored 3 my apps to Mercato, no problems so far. Though I only use 1 non-consumable IAP.
If I understood correctly you didn’t have any issues in your non-bitcode app. I think that’s the key, you don’t need to do anything on your end I guess. SSK is pretty much on hold anyway.
I moved away from SSK to SK2 now because I couldn’t afford messing around with build settings etc. and releasing a potentially breaking update so I have released whatever worked with TestFlight (automatic Sandbox) accounts and released that.
Can everyone here comment their bitcode configurations? This may actually be the issue here. Checked with another app so so far we have
@sabiland I’m not sure if I understood what apps of yours are bitcode and which ones aren’t - can you elaborate the missing info?