4.3

I believe your question is - how can I transfer IAPs purchased under one or more apps to a new 'container app' that I am creating to satisfy Apple's 4.3 issue.Revise the current app so it:1) flashes an introductory screen telling the user that the app functionality has been transferred to a new container app that they can download for free from the App Store. Include a link to that new app. Apologize for this inconvenience caused by Apple's new policy. Tell the user that this will allow them to access multiple 'thingies' (e.g. Barber shops, movie theaters, museums) all under the new app. 2) load the user's purchased IAPs into their key-value file in their iCloud account or use the shared space in the keychain or a shared NSUserDefaults file3) Tell App Review in the review notes that this revision is being pushed into the App Store to switch users to the new container app.Create a new container app that looks at the shared space to credit the user with their IAPs.

4. 3 Design: SpamGuideline 4.3 - DesignYour app provides the same feature set as many of the other apps you've submitted to the App Store; it simply varies in content or language. Creating multiple Bundle IDs of the same app is not appropriate. Next Steps To resolve this issue, please combine apps with similar feature sets into a single container app. You should differentiate varied content within your app by categorizing elements into groups, using the in-app purchase API, and location services to deliver content to users. Once you have done so, please reply to this message via Resolution Center indicating the app name and Apple ID of any container apps submitted under your Apple Developer Program account.

Since it takes a day or two to try and verify anything on this problem (no luck so far with anything I tried), francisaugusto, can you tell me if you're accessing the extension delegate from your complication controller at any point? In my early tests, it looked like the app could work indefinitely for as long as the complication didn't need to access the extension delegate (or extension delegate to access the complication controller). I had a setup where I would just show the time of the latest refresh on the complication, and I'd initiate the complication server refresh on the extension delegate, without setting any chanel of communication between the extension delegate and complication controller.Can you also tell me are you forcing the main thread execution onto anything background tasks related in your extension delegate methods? I was all along forcing the task completion onto the main thread, as per some suggestion I've read somewhere, but now I'm running a test where I've eliminated all main thread fo

I just updated to the latest watchOS 4.3 beta 3 (15T5187e) and the problem is resolved. The cards now show up again and you can use them for payment with Apple Pay.

I had chats with a few people from the review team.These are considered to be spams according to the guideline 4.3.- No similar app is allowed under your account. When they say similar, it simply means its appearance are alike. Even if targeted users are different, no similar app is allowed. Also they may say they are made using the same frameworks, it's nothing to do with the frameworks we think. It simply means they look similar. Even if the two apps are built upon completely diffrent codes (not built from a template), they are categorised as spams if they have similar user interface.- Releasing a free Lite version and a paid version is no longer accepted. Must use in-app purchase in one app instead of releasing an independent paid app. Otherwise they are rejected as spams.- Releasing upgraded new version as an independent app (like MY APP and MY APP 2) is not allowed. Old version must be removed from the store to release a new app as a different app. Otherwise they are rejected as spams.

Having the same issue with Apple Watch Series 0 and watchOS 4.3 Beta.Thank you for filing a bug report.

I am seeing the same behavior as well (Card Unavailable - Try again in a few moments). Have tried the following things but none did not resolve the issue:Restart Watch and iPhoneRemove credit cards and re-addReset the watchSign out of iCloud on iPhone and restart iPhone and Watch and sign-in again (with adding credit cards back to wallet)I have now filed a bug report with apple (#37449485), let's hope it will be fixed in the next Beta. Payments working fine in iPhone X with latest Beta, just not in WatchOS 4.3 Beta 2 with Series 0 watch.