In our app we are having feature in which we scan our qr and shows an ARScene with floating images or texts(based on the qr data) in our app.From this screen we can move to the Home page of the app with a button click as well.
This was working fine till iOS16.After we updated to iOS 17 what we observe is that once the ARScene is dismissed and the next screen are loaded, there will not be any touches recognised in the positions where there used to be the ARScene.
For floating images the ARScene is the entire screen and so in this case the next screen wont have any touch at all
For floating texts the ARScene is the top part of screen and so in this case the next screen wont have any touch in the top half only.
This issue seems to go away once we minimise the app and open again.
Example: Consider a navigation stack with 3 viewcontrollers A, B and C. The AR content is present in B.
If we load the AR content in B and move to A or C those screens are unresponsive at the positions where the ARScene was loaded
But If we dont load the AR content in B i.e just open B and move to A or C those screens have no issues.
Gokul_JD
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
Post
Replies
Boosts
Views
Activity
In our app we are having feature in which we scan our qr and shows an ARScene with floating images or texts(based on the qr data) in our app.From this screen we can move to the Home page of the app with a button click as well.
This was working fine till iOS16.After we updated to iOS 17 what we observe is that once the ARScene is dismissed and the next screen are loaded, there will not be any touches recognised in the positions where there used to be the ARScene.
For floating images the ARScene is the entire screen and so in this case the next screen wont have any touch at all
For floating texts the ARScene is the top part of screen and so in this case the next screen wont have any touch in the top half only.
This issue seems to go away once we minimise the app and open again.
Example: Consider a navigation stack with 3 viewcontrollers A, B and C. The AR content is present in B.
If we load the AR content in B and move to A or C those screens are unresponsive at the positions where the ARScene was loaded
But If we dont load the AR content in B i.e just open B and move to A or C those screens have no issues.