Closed MyBuzzTechnologies closed 1 year ago
news ?
same situation, any news about that
Fixed on new version 6.0.0-beta1
Unfortunately, this is still a problem and hasn't been fixed. I thought it had but was my mistake (the app was still using FMX rather than Skia).
Could you please re-open this and investigate?
@MyBuzzTechnologies Thank you very much for the feedback! Please, apply the last fix: https://github.com/skia4delphi/skia4delphi/commit/f218d967d7b189f7c52b91eedc5e3b4ff0d07492
Thank you, that seems to have worked. Thank you for fixing this so quickly!
The fix was included on new release: v6.0.0-beta2
Reproduced with Skia4Delphi 5.0.0 Delphi 11.2 Android build (64 bit) of any FMX app on specific devices.
We have a strange issue which is only occurring on certain devices, but we've had over 2000 reports of the crash from various low-end Android devices logged in the Play Store developer console. Higher end devices (such as most modern Samsung or Huawei are working ok).
If you set GlobalUseSkia:=False (or don't enable Skia for the project) it works perfectly and can be put into the background and restored without any problems. This is definitely related to Skia4Delphi somehow.
We have a wide range of devices which don't demonstrate this problem so may be related to a specific chipset or implementation issue. I've included the details of a device we can produce on 100% to see if it helps, along with the crash logs and SysLog from the device at time time of crash.
Downgrading to Skia4Delphi v4.1.1 resolved this issue so it's a new problem in v5.0.0
If you'd like me to test any potential fixed version I'd be happy to assist so please let me know.
Device: Oppo A16s Model: CPH2271 CPU: Helio G35 OctaCore RAM: 4GB GPU: PowerVR Rogue GE8320 Android: Android 12.1, ColorOS 12.1
Crash Log from LogCat
Stack Trace from the app at time of crash