Try this
if let pdfData = pdfView.document?.dataRepresentation() {
let printInfo = UIPrintInfo(dictionary: nil)
printInfo.jobName = "page"
printInfo.outputType = .general
let printController = UIPrintInteractionController.shared
printController.printInfo = printInfo
printController.showsNumberOfCopies = true
printController.printingItem = pdfData
printController.present(animated: true, completionHandler: nil)
}
I hope this helps.
teejayhh
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Sydney, NSW, Australia
Post
Replies
Boosts
Views
Activity
just want to mention that the login page is displayed from different sub.domain. - sso.domain.com -> app.domain.com when switching to app.domain.com then we can see that behaviour described above.
Its Aug 2022 and this is still an issue. Our app needs to support iOS 12/13 and we have no way of effectively testing our app. So I guess the only way apple expects us to work is to feature flag our app and remove all audio components on app start via a launch argument? If anyone from apple will ever look here they will tell you, to create an issue report on their feedback site. The issue with that is that no is ever looking there either. Time is on their side, unfortunately for us devs who need to deal with these issues it is giant waste of time.
We have the problem that our canvas web app seems to reach that memory limit much more often when its run in our iOS app. When its run in safari we have not seen issues reported like that. There must be a difference in memory allocation between an app wkwebview process and a safari wkwebview process. And if there isn't one what is safari doing to recover from those memory issues.
Cheers Thomas
Why is this still a problem. We recently tried to migrate our build machines to an m1 Mac mini and run into the exact problem with the sims. Its absolutely mind boggling that this issue is still around and there is ZERO acknowledgment from apple side. For us we had to disable all sounds / videos using AVFoundation to get our tests to run, which absolutely unacceptable.
How can this still be an issue @Apple. Ever since Big Sur the backwards compatibility went to bits and pieces and required me to install Catalina on a different partition to test anything below below iOS 14. On top I can't run anything above 14.4 because of different issues. Its a mess.
Did you find a way around this? We are having the same issues.