Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.3.X, 2020.1.X
Votes
0
Found in
2019.3.4f1
Issue ID
1233569
Regression
No
[iOS] ReplayKit.APIAvailable returns 'false' on the first call on iOS 13 devices
Steps to reproduce:
1. Download the attached project (replaykit-api-test.zip)
2. Switch to iOS and build
3. Build and deploy Xcode project to iOS 13 device
4. When launched, click 'Check APIAvailable' button
5. Notice the text that shows ReplayKit.APIAvailable value will change to 'false'
6. If you click 'Check APIAvailable' more than once, the subsequent times it will correctly return 'true'
Reproduced with: 2018.4.19f1, 2019.3.4f1, 2020.2.0a4
Tested with:
iPhone X (iOS 13.3) (Reproduced)
iPhone 11 Pro Max (iOS 13.3) (Reproduced)
iPad Pro (iOS 12) (Not reproduced)
iPhone 6 (iOS 12.2) (Not Reproduced)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment