Where did you get that windowNumber is UInt32 ? Doc states: var windowNumber: Int { get } On 32-bit platforms, Int is the same size as Int32, and on 64-bit platforms, Int is the same size as Int64. But never a UInt32. Why do you need converting from Int to UInt32 ?

You should contact support. It looks like those deletions and resubmissions have caused some mess. The other app has no issus, so there is no problem with your account.

That's a long known issue, when radius is between 1/3 and 1/2 of the side size. Detailed analysis here and, even more interesting, a solution with addArc(tangent1End: …): https://stackoverflow.com/questions/74623415/uibezierpath-bezierpathwithroundedrect-the-cornerradius-value-is-not-consistent

Removing the submission and resubmitting is not the best thing to do. I notice it may cause problems. You should contact support to clarify.

@iDepth from your screenshots, we can see that the new design frees space for the app's content. Isn't it a very good thing ?

Do you use a site generator to create your web site ? If so, they usually have tools or plugins to create contact forms. For instance, if you use WordPress: there are templates which include directly a contact form generator or you can add a plugin, such as contact-form 7 and there are detailed tutorials for using: such as: https://wpmarmite.com/en/contact-form-7/ Hope that helps.

Not sure you can do it on your own. Did you contact support for help ? To avoid such problem, I use a different scheme for build and version. version is the classical x.y.z and for build, I use the date 20250614. I find there is much less risk of confusion.

I had to refresh my mind on FFT. Found this interesting reference, may be of interest for those of us who need as well. https://www.analog.com/media/en/technical-documentation/dsp-book/dsp_book_Ch31.pdf

Really strange. Not sure of the explanation, but looks like the VStack is not reevaluated when popover is called. But, if added a Text in the VStack, and it works OK. VStack is reevaluated. var body: some View { VStack { Button("xxxx") { print("Button") visableHiddenMenu = true print("visableHiddenMenu \(visableHiddenMenu)") visable.toggle() } .popover(isPresented: $visable) { VStack { let _ = print("visableHiddenMenu2 \(visableHiddenMenu)") Text("Popover presented \(visableHiddenMenu)") } .onAppear { print("appear \(visableHiddenMenu)") visableHiddenMenu = visableHiddenMenu } } Text("Popover visible \(visableHiddenMenu)") } .padding() } In log: Button visableHiddenMenu true visableHiddenMenu2 true appear true visableHiddenMenu2 true Note that visableHiddenMenu2 true appears twice, showing Stack is reevaluated. PS: what is the purpose of line 19 ?

Hope you have a recent backup somewhere. You should. To create an info.plist: In Xcode, File > File > File from template (or cmd N) select Property List in Resource section name it info (Info.plist) Then populate it as needed. Typical content, in source code format: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>CFBundleDevelopmentRegion</key> <string>$(DEVELOPMENT_LANGUAGE)</string> <key>CFBundleDisplayName</key> <string>YourAppName</string> <key>CFBundleExecutable</key> <string>$(EXECUTABLE_NAME)</string> <key>CFBundleIdentifier</key> <string>$(PRODUCT_BUNDLE_IDENTIFIER)</string> <key>CFBundleInfoDictionaryVersion</key> <string>1.0</string> <key>CFBundleName</key> <string>$(PRODUCT_NAME)</string> <key>CFBundlePackageType</key> <string>APPL</string> <key>CFBundleShortVersionString</key> <string>$(MARKETING_VERSION)</string> <key>CFBundleVersion</key> <string>$(CURRENT_PROJECT_VERSION)</string> <key>ITSAppUsesNonExemptEncryption</key> <false/> <key>LSRequiresIPhoneOS</key> <true/> <key>NSCameraUsageDescription</key> <string>Text to authorise camera access.</string> <key>NSPhotoLibraryUsageDescription</key> <string>Text to authorise album access.</string> <key>UIApplicationSceneManifest</key> <dict> <key>UIApplicationSupportsMultipleScenes</key> <true/> <key>UISceneConfigurations</key> <dict> <key>UIWindowSceneSessionRoleApplication</key> <array> <dict> <key>UISceneConfigurationName</key> <string>Default Configuration</string> <key>UISceneDelegateClassName</key> <string>$(PRODUCT_MODULE_NAME).SceneDelegate</string> <key>UISceneStoryboardFile</key> <string>Main</string> </dict> </array> </dict> </dict> <key>UILaunchStoryboardName</key> <string>LaunchScreen</string> <key>UIMainStoryboardFile</key> <string>Main</string> <key>UIRequiredDeviceCapabilities</key> <array> <string>armv7</string> </array> <key>UISupportedInterfaceOrientations</key> <array> <string>UIInterfaceOrientationPortrait</string> <string>UIInterfaceOrientationLandscapeLeft</string> <string>UIInterfaceOrientationLandscapeRight</string> <string>UIInterfaceOrientationPortraitUpsideDown</string> </array> <key>UISupportedInterfaceOrientations~ipad</key> <array> <string>UIInterfaceOrientationPortrait</string> <string>UIInterfaceOrientationPortraitUpsideDown</string> <string>UIInterfaceOrientationLandscapeLeft</string> <string>UIInterfaceOrientationLandscapeRight</string> </array> </dict> </plist>

Bug corrected in Xcode 26ß. I closed the bug report. Thanks to all.

You have to ask to moderator. One way may be to mark your own post as Duplicate.

I did my tests on MacOS 15.5 with Xcode 16.4 and simulator 18.4. Could not see the issue there. So bug report is best way to go on now.

Refreshing to read such positive comments. Enjoy.

Do you want to upgrade or downgrade (from which version ?) If your device supports iOS 15, settings > General > Software update will give you access to upgrade. So, what is precisely the problem ?