Adding widgets doesn't work (possible Android beta issue)

[deathblade666]

Describe the bug
When trying to add a widget the app either crashes or returns to the Home Screen with no widget added. It's a little strange cause sometimes it does work for certain widget but most the time it does not. As the title states this could be an issue introduced in the current Beta branch of Android. I saw mention on another issue where the dev does not have direct access to a device to run the beta on so i wanted to put this in to make sure it was known and could be looked into after full release if its related.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on add widget
3. Select a widget
4. See error

Expected behavior
For a widget to populate on the screen

Screenshots
Please add screenshots to help explain your problem. You can upload images directly to Github, please do not use an external website to host your images.

Additional information

• App version: Latest 3.17 - 3.21.1
• App installed via: (f-droid, Play Store, debug APK): F-Droid/github

Additional context
Add any other context about the problem here.

Was able to pull some potentially relavent logs via adb logcat

08-16 11:27:30.188 22072 22072 V PaintChips: building widget: shade rows=13, color columns=5
08-16 11:27:30.192  4242  4838 D ForegroundUtils: UID: 10145 deleted.
08-16 11:27:30.206  1017  1017 D Zygote  : Forked child process 601
08-16 11:27:30.207  1798  1854 I ActivityManager: Start proc 601:fr.neamar.kiss/u0a145 for top-activity {fr.neamar.kiss/fr.neamar.kiss.MainActivity}
08-16 11:27:30.224   601   601 I fr.neamar.kiss: Using CollectorTypeCMC GC.
08-16 11:27:30.229   601   601 E fr.neamar.kiss: Not starting debugger since process cannot load the jdwp agent.
08-16 11:27:30.233   601   601 D nativeloader: Load libframework-connectivity-tiramisu-jni.so using APEX ns com_android_tethering for caller /apex/com.android.tethering/javalib/framework-connectivity-t.jar: ok
08-16 11:27:30.243  4242  4838 D ForegroundUtils: Foreground UID status:
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10071 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10139 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10145 is in foreground: true
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10178 is in foreground: true
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10197 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10210 is in foreground: true
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10215 is in foreground: true
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10216 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10220 is in foreground: true
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10226 is in foreground: true
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10228 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10233 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10236 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10254 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10256 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 10390 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 1001000 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 1010148 is in foreground: true
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 1010220 is in foreground: true
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 1010293 is in foreground: false
08-16 11:27:30.243  4242  4838 D ForegroundUtils: UID: 1010593 is in foreground: false
08-16 11:27:30.255   601   601 D nativeloader: Configuring clns-7 for other apk /data/app/~~pEzxy8mxyfQnGQEADrcdYQ==/fr.neamar.kiss-906Iuaz80_6eXfEYNuGcpQ==/base.apk. target_sdk_version=33, uses_libraries=, library_path=/data/app/~~pEzxy8mxyfQnGQEADrcdYQ==/fr.neamar.kiss-906Iuaz80_6eXfEYNuGcpQ==/lib/arm64, permitted_path=/data:/mnt/expand:/data/user/0/fr.neamar.kiss
08-16 11:27:30.262   601   601 V GraphicsEnvironment: Currently set values for:
08-16 11:27:30.263   601   601 V GraphicsEnvironment:   angle_gl_driver_selection_pkgs=[com.android.angle, com.linecorp.b612.android, com.campmobile.snow, com.google.android.apps.tachyon]
08-16 11:27:30.263   601   601 V GraphicsEnvironment:   angle_gl_driver_selection_values=[angle, native, native, native]
08-16 11:27:30.263   601   601 V GraphicsEnvironment: fr.neamar.kiss is not listed in per-application setting
08-16 11:27:30.263   601   601 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
08-16 11:27:30.266  1114  1751 D audioserver: logFgsApiEnd: FGS Logger Transaction failed, -129
08-16 11:27:30.270  1036 28369 W amcs_ext_file: update_third_party_effect_amcs_data:fail to send ioctl amcs, ret -1
08-16 11:27:30.270  1036 28369 W audio_hw: fail on interact with audio_amcs_ext.so -1
08-16 11:27:30.270  1036 28369 D audio_hw_waves: update_sink_info_from_usecases: update amcs, instance id 1, volume 150 0 0 0 0 0 0 0 0 0
08-16 11:27:30.270  1036 28369 D audio_hw_output_stream: update stream 1 active 0 gain 0.000000
08-16 11:27:30.274   601   635 I DMABUFHEAPS: Using DMA-BUF heap named: vframe-secure
08-16 11:27:30.302   601   601 D CompatChangeReporter: Compat change id reported: 210923482; UID 10145; state: ENABLED
08-16 11:27:30.335   601   702 D CompatChangeReporter: Compat change id reported: 183155436; UID 10145; state: ENABLED
08-16 11:27:30.337  1798  4293 D ShortcutService: Getting shortcuts for launcher= fr.neamar.kissuser=0 pkg=null

[deathblade666]

Wanted to add, other launchers have a widget permission dialog appear when adding widgets for the first time after a fresh install, this does not appear to be occurring with KISS, not sure if it's strictly needed or just a legacy component in those other apps, but figured it'd be worth mentioning

EDIT: I tried on another phone running android 14, and the issue isn't present. So looks like it very likely could just be a 15 beta thing.