Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2019.4.10f1
2020.2
Issue ID
1279284
Regression
No
[iOS 14][Xcode 12] GKAccessPoint is displayed in Portrait orientation and appears in the wrong position of the screen
How to reproduce:
1. Open the attached 'GameCenterTest.zip' project
2. Switch Platform to iOS
3. Build for iOS and open the Xcode project
4. Make sure Game Center capability is enabled in Xcode and Game Center user is set in device settings
5. Deploy Xcode project to an iOS 14 device
6. When application is launched 'Press Show Access Point' button
7. Press 'Show Achievements' button
8. Close the opened window
Expected result: GKAccessPoint is displayed in landscape orientation and appears in the top-left corner
Actual result: GKAccessPoint is displayed in portrait orientation and appears in the bottom-left corner
Reproducible with: 2019.4.11f1, 2020.1.7f1, 2020.2.0b4
Couldn't test with: 2018.4.27f1 (launched app is blank)
Reproducible with:
- iPad 6th gen (iOS 14.2)(Xcode 12)
Could not test with:
- iPhone XR (iOS 13.4.1) (leaderboard's data is not available when 'Press Show Access Point' window opens, leaderboard works fine in other apps)
- iPad Pro 12.9 1st gen (iOS 13.4.1) (because of errors in Xcode)
Notes:
- Tested using macOS 11.0 Beta(Big Sur) and Xcode 12. Customer emphasized that the issue reproducible using Xcode 12 and iOS 14. No sure if it reproduces with Xcode 11)
- GKAccessPoint seems to be an iOS 14 feature what makes the app not testable on iOS 13 devices
- Game is set to portrait in PlayerSettings and set to landscape in Awake. Screen.orientation = ScreenOrientation.Landscape;
- Screenshot of the issue is attached in Edit
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2020.2.X):
The GKAccessPoint respects the settings in Xcode's "Supported Orientation" section