Potential iOS26 regression on AASA file not download on app install

Question

Created 1w

Replies 6

Boosts 1

Participants 4

Our app uses Auth0 with HTTPS callback, we've found the issue where AASA file is not ready immediately when app is initially launched, which is the exact issue from the above link.

The issue seems mostly fixed on later versions on iOS 18, however, we are seeing some indications of a regression on iOS 26. Here's some measurement over the last week.

| Platform          | iOS 18     | iOS 26 |
|---------------|----------|--------|
| Adoption rate | 55%         | 45%    |
| Issue seen      | 1               | 5          |
| Recover?        | Yes           | No       |

This only 1 iOS 18 instance was able to recover after 1 second after the first try, however, all iOS 26 instances were not able to recover in couple tens of seconds and less than 1 minute, the user eventually gave up.

Is there a way to force app to update AASA file?
Are there some iOS setting (like using a VPN) that could potentially downgrade the AASA fetch?

Related Auth0 discussion:

https://community.auth0.com/t/ios-application-not- recognizing-auth0-associated-domain/134847/27

Boost

Answer 1

DTS Engineer OP

Apple

1w

Thank you for your efforts and the insightful post demonstrating the degradation from iOS 18 to 26. The description is comprehensive, and I believe we are prepared to file a bug report. However, kindly provide a link to your AASA file and the app ID responsible for downloading the AASA file when submitting the bug report as well as the sw_util file that contains the logs when the file gets downloaded.

I am also very interested in knowing if any other developer has observed a regression from when the file is downloaded.

Once you open the bug report, please post the FB number here for my reference.

If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why?

Albert Pascual   Worldwide Developer Relations.

0

Answer 2

cbeaversenlevelall OP

6d

I'm seeing a similar issue across any/all simulators. I filed FB20871095 for my issue.

0

Answer 3

DTS Engineer OP

Apple

6d

@cbeaversenlevelall thanks for filing the bug for this issue. This is great, and will be routed to the correct team. Give engineering sometime to look and investigate the issue.

You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label "Resolution." We're unable to share any updates on specific reports on the forums.

For more details on when you'll see updates to your report, please see What to expect after submission.

Albert Pascual   Worldwide Developer Relations.

0

Answer 4

PantryPilot OP

2d

I'm seeing a similar issue unfortunately.

It's frustrating that ASWebAuthenticationSession and universal links seem to be the recommended approach to authenticate users against a web service, but they rely on AASA verification.

0

Answer 5

DTS Engineer OP

Apple

2d

@PantryPilot Can you please submit a bug as well following my link? https://developer.apple.com/forums/thread/712889

Would you post the FB number here.

Thanks

Albert Pascual   Worldwide Developer Relations.

0

Answer 6

PantryPilot OP

7h

@DTS Engineer I've submitted a bug report with ID FB20925084.

Unfortunately I wasn't able to provide too many details.

I'm not able to reproduce this issue on iOS 26 but it was reported by one of my beta testers and the app review team. The issue is now blocking submission of my app to the app store.

I'm surprised there are not more reports of this issue. I'd had thought it would affect many apps that use web services or OAuth to authenticate.

0