Thanks for your attention @JeffDUnity3D . I saw your suggestion in another post and despited I compared the code before creating this topic, I did it again (you can always miss something little but important). So the initialization logic looks the same but I need to verify:
-
MyIAPManager.cs: on line 32 the initialization is started only if only m_StoreController is null, but on line 46 we use IsInitialized() method which checks both m_StoreController and m_StoreExtensionProvider. Does it mean that if we do auto initialization then we should do this only if m_StoreController is null because there is a chance that it will not be null while m_StoreExtensionProvider will be null? (probably in the middle of previous initialization) or that’s just typo?
-
The solution provided in Sample IAP Project v2 assumes that we should NOT retry initialization in case of failure (in our case it’s every 60 sec)?
To be honest, I like the logic: instead of trying to initialize IAP every N second, we can try to do it at app’s start and then when store window will be openned or whatever pre purchase user action will occure. At least, this should reduce the chance that initialization will be in the middle, when app will be sent to background and the issue mentioned in inital post will arise.
-
Taking in an account that this non fatal issue appeared only after applying this few lines. Do not Unity team plan to investigate the case, as it was reported on GitHub on Nov 14, 2020?
-
I also noticed one extra line: SetDeferredPurchaseListener(OnPurchaseDeferred) and according to this topic , seems like blank listenere must be set. Could you please confirm?
Thank you in advance for your time and help!