İOS 26 beta battery %1

I slept on this issue overnight and thought it has something to do with the deployment of Xcode 26. It happens that it was released yesterday, I'm going to install Xcode 26 to see what happens.

I would delete existing subscription plans and create new ones with different reference names and product IDs. There was a time when existing IAP products went unusable after the reviewer rejected the app body itself. I guess that was a decade ago.

Thank you for your post. If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, make sure to: Provide specific reasons why you believe your app complies with the App Review Guidelines. Submit only one appeal per rejection. Respond to any requests for additional information before submitting an appeal. Once you have submitted the appeal we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they've completed their investigation.

Found this thread when researching an issue with the same log message in a pure SwiftUI app. There's a nasty layout/animation associated with what I'm seeing (but I'm not sure it's related to the log). A sample project to repro is attached to FB20272800 (apologies for hijacking OP's thread, but I thought it might perhaps be interesting to them that issue reproduces in iOS 26 without using a UIHostingController in our own code. A simple Menu suffices)

Just tested this and see Not Valid Before=Tuesday, September 16, 2025 at 1:37:53 PM Pacific Daylight Time Not Valid After=Friday, October 16, 2026 at 1:37:52 PM Pacific Daylight Time Perhaps it was a glitch at the time

The ability to stay connected to a BLE device is not something that can be enhanced via an app. A whole lot will depend on the hardware, like antenna design; environment, like distance, RF interference; materials between the two devices; and various connection parameters including but not limited to the power profiles. Assuming you have no control whatsoever on any of these, the only thing you can do in the app is to make sure you are able to connect as quickly as possible when (not if) the connection drops. This means you need to make sure you have implemented Bluetooth State Restoration, so your app gets relaunched even if the app has been terminated in the background by the system. The document Performing Long-Term Actions in the Background explains how to implement this. The second thing you need to do is to make sure you issue a connectPeripheral command as soon as your app gets the callback that the connection has dropped. It is advisable to keep the CBPeripheral object from the last connection and send

Please see the Configuring Your App to Use Alternate App Icons that uses Icon Composer files and supports iOS 18 or later. Note: The sample only uses Icon Composer files. No old icons.

Thanks for the comments/answers. I assumed that the type of file should be set by the Open as context menu. But, I now understand to use the file inspector to set the type. I still have a bit of an issue that in one of my projects, the editor aggressively suggests text completion with swift entities.