The purpose of the forum is not to discuss performance of third party apps. In fact, I don't care reading about gaming performance on pubgmobile in this forum. Have a good day and contact the app developer forum.

@Forums Product Manager Thanks for the answer. It's good to know there is no bot and an intent to adapt the answer to spams.

Have a look here, https://community.revenuecat.com/general-questions-7/ios-code-error-23-none-of-the-products-registered-in-the-revenuecat-dashboard-could-be-fetched-from-app-store-connect-3680 Maybe that's due to the declared list of active countries for subscription

Does it work in simulators iOS 16 ? Have you found any device where it works with iOS 16 ? How is it you discover the issue only now ? Did it work in the past ? Did you change Xcode version in between ? Can you test with Xcode 16 ? It seems that it affects older devices iPhone 8, iPhone 12, iPhone 8 Plus, iPhone 8 Plus So is it only iOS related ?

It's a fact that the rules on Appstore are much more strict than on other platforms, specially for money games like casino. One may appreciate or not, but that's it. So, expecting to "replicate" what was done on other platform when submitting to Appstore is not the best approach. In addition, as darkpaw explained, it is really important to discuss with reviewer in good faith, transparency and of course respectful way (as reviewers always do) even to explain why you think their decision was wrong. Doing differently may lead to unexpected consequences. BTW, if your account was banned, you will ne be able to publish on Appstore. But you may try to appeal this ban (need to have convincing arguments).

I have such a case with a basic and pro versions which share some code. What I do each time I submit a new release, is to write a comment to reviewer, explaining (both for basic and Pro) what are the significant extra functions in Pro. Extra capabilities must be significant.

I would do it in onAppear: struct Foo { var valid : Bool } struct FooView: View { var foo: Foo = Foo(valid: false) var body: some View { Text("Check assert") .onAppear() { assert(foo.valid) } } } Other option is to do it in init()

Better than complaining would be to file a bug report, asking for enhancement.

You should file a bug report. And remember that's a beta, which per essence, may have (critical) bugs. So, it should only be installed in a secondary device.

Your problem description is not very helpful. You probably miss a step, but impossible to say without more information. Could you post a screenshot of? Which item are you precisely trying to add ?

Did you try to define a .frame for the HStack ? Note: this does not compile Tab("Main Tab", systemImage: "tray.and.arrow.down.fill") {

Hopefully, it is not possible, for the reasons @darkpaw explained.

Screenshots have nothing to do with ReactNative.   Screenshots were supplied showing everything faded How did you take the screenshots ?

@baraupp Exactly same error here. With MacOS 14.7.1, Xcode 16.2 or 15.3. WatchOS and iPhone all updated to last version. And all on the same wifi… Finally, after many retries, and just waiting for more one hour, finally, Xcode fetched symbols. And is now succeeded to connect the Watch.

Could you describe your use case more in detail ? Is it the text from your app, or any text (like a Finder file name) that may appear on screen ? If the former, is it a NSTextField ? Do you know which window it is in ? And then, with the window position you should be able to compute text position. If the latter, text may just be an image, for OCR may be the best way to go. But effectively may be slow.