Last week, there was an issue tagged in the 'Known Issues' section of the patch notes (screenshot attached). We have encountered this glitch and while I am working on a work-around I was hoping that it would be flat out fixed soon.
I look today and I note that that line has been removed from the 'Known issues'.
Has this already been fixed (perhaps on Apple's end? It seems related to upgrading to 14.2) If it hasn't been resolved why has it been removed from 'Known issues'? (EDIT: I stand corrected - I was looking in iOS known issues, not Unity known issues. It is still there)
This was a major problem for us. We had an exhibition launch in Toronto and while things seemed fine during the week we tested the event, right after launch we had ALL kinds of problems with black screens ALL on iOS. Our clients reported having upgraded their phones to 14.2 during that week. Having seen this in the patch notes had me a little relieved, but I now see that has been removed.
Our clients are NOT happy about this and it has been a huge hamper in our working relationship. Things were fine before the launch and then all of a sudden this was happening with no changes made to the app itself.
Please advise on an ETA or a work-around I can do. I've already created a delay of 15 seconds between menu load and AR CAM scene-change so that if the user tries to go straight to the AR CAM from the menu (rather than browsing the menu) it'll create more of a delay to prevent rapid-switching.
Attachment | Size |
---|---|
![]() | 68.97 KB |
The app repository isn't in a state that's easy to transfer at the moment (it's in separate submodulees that need different permissions) We are going to revise this in februrary. If it comes to that, please let me know how we can best get the repo to your team (maybe we can add your GitHub account to our permissions list?)
In the meantime - we found a user-driven work around. If the app gets minimized and then you switch back to it, the image clears itself.
I strongly suspect that you have code that triggers something when the app recovers after being minimized. Is there a way for me to call that function directly after a few seconds? If so I may be able to trigger whatever refreshes it automatically to fix the issue. (We are already calling OnSurfaceChange(screen.width, screen.height) That was an early fix that was needed for Android way back several years ago)