-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Link weakly to NewsstandKit #18606
Labels
bug
If an issue is a bug or a pull request a bug fix
high-priority
This is a high-priority issue or pull request
Milestone
Comments
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Aug 2, 2023
It seems that Apple will completely remove the NewsstandKit framework from iOS 17. This poses a problem for existing apps that link with NewsstandKit: they will crash at launch. Solve this by always linking weakly with the NewsstandKit framework; this way any apps that link with it will keep working if the framework ends up being removed by Apple. Fixes dotnet#18606.
rolfbjarne
added a commit
that referenced
this issue
Aug 3, 2023
It seems that Apple will completely remove the NewsstandKit framework from iOS 17. This poses a problem for existing apps that link with NewsstandKit: they will crash at launch. Solve this by always linking weakly with the NewsstandKit framework; this way any apps that link with it will keep working if the framework ends up being removed by Apple. Fixes #18606. Fixes dotnet/maui#16316.
vs-mobiletools-engineering-service2
pushed a commit
to vs-mobiletools-engineering-service2/xamarin-macios
that referenced
this issue
Aug 3, 2023
It seems that Apple will completely remove the NewsstandKit framework from iOS 17. This poses a problem for existing apps that link with NewsstandKit: they will crash at launch. Solve this by always linking weakly with the NewsstandKit framework; this way any apps that link with it will keep working if the framework ends up being removed by Apple. Fixes dotnet#18606.
vs-mobiletools-engineering-service2
pushed a commit
to vs-mobiletools-engineering-service2/xamarin-macios
that referenced
this issue
Aug 3, 2023
It seems that Apple will completely remove the NewsstandKit framework from iOS 17. This poses a problem for existing apps that link with NewsstandKit: they will crash at launch. Solve this by always linking weakly with the NewsstandKit framework; this way any apps that link with it will keep working if the framework ends up being removed by Apple. Fixes dotnet#18606.
rolfbjarne
pushed a commit
that referenced
this issue
Aug 4, 2023
…18606. (#18624) It seems that Apple will completely remove the NewsstandKit framework from iOS 17. This poses a problem for existing apps that link with NewsstandKit: they will crash at launch. Solve this by always linking weakly with the NewsstandKit framework; this way any apps that link with it will keep working if the framework ends up being removed by Apple. Fixes #18606. Fixes dotnet/maui#16316. Backport of #18621
rolfbjarne
pushed a commit
that referenced
this issue
Aug 7, 2023
… (#18625) It seems that Apple will completely remove the NewsstandKit framework from iOS 17. This poses a problem for existing apps that link with NewsstandKit: they will crash at launch. Solve this by always linking weakly with the NewsstandKit framework; this way any apps that link with it will keep working if the framework ends up being removed by Apple. Fixes #18606. Fixes dotnet/maui#16316. Backport of #18621
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
If an issue is a bug or a pull request a bug fix
high-priority
This is a high-priority issue or pull request
iOS 17 seems to completely remove the NewsstandKit framework.
This is problematic for apps that happen to link with the NewsstandKit framework (they crash at launch).
Ref: dotnet/maui#16316
We should look into always linking weakly with NewsstandKit (in existing stable release for .NET 7), so that existing apps won't crash when end users upgrade to iOS 17.
The text was updated successfully, but these errors were encountered: