4.3

Something similar here. Running ios 11.3 beta 6 on iphone X and watchos 4.3 beta 4 on apple watch s3. shows no mail account. setup a new account on your iphone. on watch MAIL app. I have tried restoring betas on iphone to no aval.

Oh my.... and I thought I was the only one having this problem with AppleI have four AppsPoolAppLive, DartsAppLive, SnookerAppLive and LeagueAppLive, all have different features, logos, text and all are marketed brands.All use a core scoring feature (obviously)All these were on the App Store before this 4.3 policy was introduced or changed.Now Apple wants me to produce one App that has an initial menu to pick one of the sportsCoding this is easy enough, but why would I want to do this?Each App has it's own identity and brand by design. Each is linked to a customer website , for example mktpl.poolapplive.com each has been advertised seperately at cost to myself. I want customers to find my App by simply typing in the brand name as they already do on both Android and iOSI am not spamming. I find this really quite insulting, if it wasn't for developers like myself Apple would be selling their devicesWe also pay for this service (unlike other app stores)I agree spamming should not be allowed, but this is

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.