Post marked as Apple Recommended
A gentle reminder: Please file feedback via Feedback Assistant. "Me too" / "same issue" responses are not actionable. A feedback report, with the name and numerical Apple ID of your app, the version of TestFlight, the time the issue happened, and any other details, is actionable.
Additionally, this issue was confirmed resolved in December 2022. Please ensure you are using a recent version of TestFlight (at least3.2.3) and that you've submitted an updated build of your app after December 2022.
If you are still seeing this error after December 2022 and you've confirmed the above two items, it's likely an issue that is unique and specific to your app, rather than a wide-spread issue. A feedback report with details will allow the TestFlight engineering team to investigate.
Thanks,
Jason.
Post marked as Apple Recommended
Hello everyone,
The original issue reported was resolved in recent versions of iOS and iPadOS.
The fix is available on iOS and iPadOS 16.2 or later.
For devices incompatible with iOS and iPadOS 16, the fix has also been back-ported to iOS and iPadOS 15.7.3 or later.
Note that loading a Smart App Banner requires connecting to App Store servers and the app must be available for sale in the App Store.
Additionally, for privacy reasons, a Smart App Banner is only supported in regular browsing, not Private Browsing.
Please confirm
The device is running an OS containing the fix.
The device can connect to the App Store.
The app is available for sale in the App Store.
You are not using Private Browsing.
If all four are true, please file a new bug report with complete information so the engineering team can investigate.
(I've tested as many examples as I can from the recent issues above and all work for me in iOS 16.6, for example.)
Thanks,
Jason.
Post not yet marked as solved
Please don't offer to share Apple-owned software.
—Jason.
Post marked as Apple Recommended
Hi folks,
I want to be clear: this issue is specifically about copying files from DeviceSupport.
Discussion about what should or does work is a separate issue, and I encourage you to file feedback if you find any limitations that don't meet your expectation.
We want to run the app on ios17 devices with lower versions of xcode, but it is strange that the iOS DeviceSupport in xcode15 is only up to 16.4, not 17. I don't understand how xcode15 can run the app on iOS17 devices
Because the way Xcode 15 beta talks to devices isn't represented in the DeviceSupport folder, because:
As the system evolves, any expectations for "how things work" could be made invalid, and this appears to be the case here.
There is quite a popular gist that people have updated for about 7 years on how to do this. It's not unusual to do.
I understand. An undocumented process happened to work (yes, for a long time), and now it doesn't. That is the nature of undocumented processes: they are subject to change, and can break things that rely on them.
Flutter is complaining about not being able to find support for iOS 17.
Sounds like Flutter may need to update their assumptions about how the system works. (I don't know why Flutter relies on that folder; that's a question for Flutter.)
—Jason.
Post not yet marked as solved
Hello @humiyatakahashi,
Please see the Offering account deletion in your app, and the included FAQs, which I believe answer your questions directly.
—Jason.
Hello @chizy,
Turning off beta updates while running a beta means you won’t get any updates: no beta updates (because you turned them off) and no ”regular” updates (because you can’t install an earlier version of the OS over a newer version without erasing/restoring your device).
If you were in the iOS 16 public beta, then installed the iOS 17 developer beta, you will need to restore your device to iOS 16 to get any future iOS 16 updates, or enable beta updates to get any future iOS 17 beta updates.
Additionally, the process of installing public beta software changed recently. It no longer uses profiles. Instead, it is tied to your Apple ID and shows up in Software Updates.
—Jason.
Hello @goatma,
Can I use On Demand Resources in my free app?
Yes.
On-Demand Resources Essentials
—Jason.
Post not yet marked as solved
Hm. A different update, perhaps?
iOS 17 beta requires macOS Ventura 13.3. Are you running macOS Ventura 13.3?
Minimum requirements and supported SDKs
—Jason.
Post marked as Apple Recommended
iOS 17 beta requires Xcode 15 beta.
Copying files from a newer version of Xcode to an older version of Xcode for any purpose was never supported. That it worked for your needs was coincidental.
As the system evolves, any expectations for "how things work" could be made invalid, and this appears to be the case here.
Please use Xcode 15 beta to work with iOS 17 beta.
For earlier OS and Xcode releases, please refer to the Minimum requirements and supported SDKs for appropriate and supported combinations.
—Jason.
Post not yet marked as solved
https://developer.apple.com/visionos/work-with-apple/
Post marked as Apple Recommended
Hello @michelf19. Can you explain what you're trying to accomplish? What do you mean by
(coping iOS 17 Device Support files from Xcode 15)
? Are you expecting to copy files from a later version of Xcode to an earlier version of Xcode? To what end?
—Jason.
Post not yet marked as solved
Hello @EntangledStudios. This is a bit outside my expertise, but how are you offering subscriptions without offering in-app purchases?
Perhaps that detail would help clarify the issue, and someone can provide a response.
—Jason.
Post not yet marked as solved
Hello @obsessive. The "update" here is likely one that you Mac needs to talk to your iPhone. That "update" is likely the macOS Sonoma beta, which is indeed not available via Software Update.
Basically, you can't install iOS 17 beta because your Mac doesn't know how to talk to an "iOS 17 beta" device yet.
(As an aside: I'm not sure how installing the ipsw solves the lack of available space to do an upgrade.)
—Jason.
Post not yet marked as solved
Hi. Perhaps I’m misunderstanding your quest. Are you asking how to remove Sign in with Apple functionality from your app, or prevent any app on the device from using Sign in with Apple?
The former is possible, if you’re not required to use SIWA: remove the SIWA code from your app).
The latter is not.
Jason.
Post not yet marked as solved
Hi. Try removing the extra quotes from around your values.
Instead of
<meta name="apple-itunes-app" content="app-id="my_app_id", app-clip-bundle-id="my_app_clip_bundle_id", app-clip-display=card">
try
<meta name="apple-itunes-app" content="app-id=my_app_id, app-clip-bundle-id=my_app_clip_bundle_id, app-clip-display=card">
—Jason.
