Google Pixel 5 showing black overlay on right side of screen in Firebase Test Lab
184 views
Skip to first unread message
Superpea LTD.
May 4, 2021, 4:46:30 AM5/4/21
to Firebase Google Group
Hi,
Does anybody know why a Google Pixel 5 might have a black overlay on the rightmost 60% of the screen when viewing the screenshots of a Robo Script in Firebase Test Lab?
All the other devices (20 or so) work perfectly.
Looks like this:
Should look like this:
Same issue happening in Google Play Developer console which uses the same framework, but only ever seen with a Pixel 5 or Google Pixel 5e:
Project is built in Unity 2017 and exported to Android Studio where it is published as an .aab and uploaded to the Developer Console and Firebase Test Lab.
Not sure if it's a Pixel 5 feature that the robot gets stuck on and a real user would know to swipe away the screen or something. Any help would be much appreciated.
Superpea LTD.
May 13, 2021, 5:27:01 AM5/13/21
to Firebase Google Group
At this point it would be good to know if anybody can ever get a Robo Test on API 30 to present coherent screenshots when they follow the build documentation. In addition to the previous build that showed no warnings in Android Studio, I've since managed to replicate this using the latest version of Unity in an otherwise empty new project:
Click on "Test Issues" and observe the sole warning:
We've been stuck on this for over 2 weeks. Please help. I can't release my app update knowing that perhaps on a significant proportion of modern API 30 devices, all of which we'll never be able to afford to buy for in-house debugging, a total crash might ruin the user experience from the second the app opens. I've posted this to Stack Overflow and can't get a response. I thought it was something wrong with my project but looks like a Unity/Firebase/Pixel issue?
The app works fine on all other Firebase physical devices running API < 30, it works fine on API 30 Emulators within Android Studio, and it works fine on my own API 30 Motorola G10. If somebody could please have a look at the massive logs that Firebase provides in our developer accounts and shed some light on what we might be doing wrong (if anything) and how we can fix it I would massively appreciate it as our app update is long overdue. If it's happening with default Unity settings this must be affecting a lot of people.
Steps:
Once complete, click on "Screenshots" and observe the black overlay over the rightmost 60% of the screen:
- Make a new folder for the project on your hard drive.
- Ensure Unity 2021 has Android Build support and modules added for the SDK and JDK:
- Ensure that Unity's external tools paths are set to "recommended":
- Use UnityHub to create a new project within Unity 2021, selecting the previously created new project folder.
- Set target platform to Android.
- Build APK with default settings (note that API 30 is apparently the highest installed and therefore the target SDK in Player settings).
- Upload APK to Firebase Test Lab and run a robo test on any of the physical devices running API 30 (Google Pixel 5e, or Google Pixel 4 when set to use API 30).
Once complete, click on "Screenshots" and observe the black overlay over the rightmost 60% of the screen:
Click on "Test Issues" and observe the sole warning:
We've been stuck on this for over 2 weeks. Please help. I can't release my app update knowing that perhaps on a significant proportion of modern API 30 devices, all of which we'll never be able to afford to buy for in-house debugging, a total crash might ruin the user experience from the second the app opens. I've posted this to Stack Overflow and can't get a response. I thought it was something wrong with my project but looks like a Unity/Firebase/Pixel issue?
The app works fine on all other Firebase physical devices running API < 30, it works fine on API 30 Emulators within Android Studio, and it works fine on my own API 30 Motorola G10. If somebody could please have a look at the massive logs that Firebase provides in our developer accounts and shed some light on what we might be doing wrong (if anything) and how we can fix it I would massively appreciate it as our app update is long overdue. If it's happening with default Unity settings this must be affecting a lot of people.
Many thanks,
Richard
Reply all
Reply to author
Forward
0 new messages