Fixed
Status Update
Comments
br...@google.com <br...@google.com> #2
Hi
when you are saying
When I create an emulator, there is no cutout hole. It appears as I use it. I tried removing it in various ways, but the same phenomenon occurs.
Could you please tell us more about how you create your AVD? Are you creating your own skin? Or did you select one of the Device proposed in the Device Manager ? (e.g. "Small Phone", "Medium Phone", "Pixel 8",...)
there is no cutout hole. It appears as I use it
We are not sure about the situation you are referring to. Some screenshots would be useful, and also a detailed description of "It appears as I use it".
Thanks
[Deleted User] <[Deleted User]> #3
Hi
Android Studio Meerkat | 2024.3.1
Pixel 9 Pro XL
Android 16.0("Baklava") | x86_64
Api: 36
======================================================================
-- AppData\Local\Android\Sdk\skins\pixel_9_pro_xl\layout
parts {
device {
display {
width 1344
height 2992
x 0
y 0
corner_radius 0 <--------------- no effect
}
}
portrait {
background {
image back.webp
}
foreground {
mask mask.webp
cutout 0 <------------------------ Deleting or changing it has no effect
}
}
}
layouts {
portrait {
width 1466
height 3101
event EV_SW:0:1
part1 {
name portrait
x 0
y 0
}
part2 {
name device
x 57
y 56
}
}
}
-- No Effect
==========================================================
The same problem occurred when using different APIs on different devices.
But after deleting all
AppData\Roaming\Google\AndroidStudio...
directories and restarting, it seems to have been resolved.
Best regards
Android Studio Meerkat | 2024.3.1
Pixel 9 Pro XL
Android 16.0("Baklava") | x86_64
Api: 36
======================================================================
-- AppData\Local\Android\Sdk\skins\pixel_9_pro_xl\layout
parts {
device {
display {
width 1344
height 2992
x 0
y 0
corner_radius 0 <--------------- no effect
}
}
portrait {
background {
image back.webp
}
foreground {
mask mask.webp
cutout 0 <------------------------ Deleting or changing it has no effect
}
}
}
layouts {
portrait {
width 1466
height 3101
event EV_SW:0:1
part1 {
name portrait
x 0
y 0
}
part2 {
name device
x 57
y 56
}
}
}
-- No Effect
==========================================================
The same problem occurred when using different APIs on different devices.
But after deleting all
AppData\Roaming\Google\AndroidStudio...
directories and restarting, it seems to have been resolved.
Best regards
[Deleted User] <[Deleted User]> #4
Cutout hole appears again. I attatch a screenshot.
br...@google.com <br...@google.com>
br...@google.com <br...@google.com> #5
Fixed in version 1.10.0. Thanks for the report!
Description
demonstration page if at all possible, or attach code.
1. Xcode's project link:
2. Video where I explain you how to trigger the bug and show you in which case the bug occurs:
Message logged:
didChangeAuthorizationStatus 1.1 default case
Beginning of .Restricted, .Denied cases.
Beginning of .Restricted, .Denied cases.
didChangeAuthorizationStatus Beginning of case .AuthorizedWhenInUse, .AuthorizedAlways.
2015-04-23 00:00:22.646 minima[33523:978518] *** Terminating app due to uncaught exception 'GMSBackgroundAppException', reason: 'Background execution would crash in this scenario'
*** First throw call stack:
(
0 CoreFoundation 0x020af746 __exceptionPreprocess + 182
1 libobjc.A.dylib 0x03ae3a97 objc_exception_throw + 44
2 CoreFoundation 0x020af66d +[NSException raise:format:] + 141
3 minima 0x002f8b04 -[GMSAsyncInitServices sharedInitWithSync:] + 198
4 minima 0x002f89c1 -[GMSAsyncInitServices initSync] + 82
5 minima 0x002f985b +[GMSServices sharedServicesSync] + 217
6 minima 0x002ead9f -[GMSGeocoder initWithConnection:] + 127
7 minima 0x002ead1b -[GMSGeocoder init] + 41
8 minima 0x000cd0f1 _TTOFCSo11GMSGeocodercfMS_FT_S_ + 33
9 minima 0x000c3719 _TFCSo11GMSGeocoderCfMS_FT_S_ + 89
10 minima 0x000be0bf _TFC6minima14ViewControllerP33_283D2901799AD1FEE675806068CAE00C32googleMapsiOSSDKReverseGeocodingfS0_FVSC22CLLocationCoordinate2DT_ + 79
11 minima 0x000c0f87 _TFC6minima14ViewController15locationManagerfS0_FTGSQCSo17CLLocationManager_18didUpdateLocationsGSQGSaPSs9AnyObject____T_ + 1735
12 minima 0x000c1293 _TToFC6minima14ViewController15locationManagerfS0_FTGSQCSo17CLLocationManager_18didUpdateLocationsGSQGSaPSs9AnyObject____T_ + 147
13 CoreLocation 0x0141fcce CLClientGetCapabilities + 23211
14 CoreLocation 0x0141f100 CLClientGetCapabilities + 20189
15 CoreLocation 0x0141bc81 CLClientGetCapabilities + 6750
16 CoreLocation 0x01415e02 CLClientInvalidate + 999
17 CoreFoundation 0x01fd1050 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 16
18 CoreFoundation 0x01fc6963 __CFRunLoopDoBlocks + 195
19 CoreFoundation 0x01fc67bb __CFRunLoopRun + 2715
20 CoreFoundation 0x01fc5a5b CFRunLoopRunSpecific + 443
21 CoreFoundation 0x01fc588b CFRunLoopRunInMode + 123
22 GraphicsServices 0x052eb2c9 GSEventRunModal + 192
23 GraphicsServices 0x052eb106 GSEventRun + 104
24 UIKit 0x028d3106 UIApplicationMain + 1526
25 minima 0x000d7a84 main + 180
26 libdyld.dylib 0x041f4ac9 start + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Operating system version: Mac OS X Yosemite 10.10.3
Google Maps SDK for iOS version: 1.9.2
Hardware model: bug happens only in the iOS simulator using Xcode 6.3 and iOS 8.3.
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************