All files access switch greyed out when trying to grant files permissions

EDIT BY CATFRIEND1; TL;DR: To everyone reading this issue. You are advised to switch to the GitHub release (APK can be downloaded from here) or the F-Droid release to get the full features of the Syncthing-Fork app without G’s restrictions.

If you’re stuck on the welcome assistant because of Android restrictions, please read https://github.com/Catfriend1/syncthing-android/pull/747 and use the emergency config export button to export your existing Syncthing config to “/storage/emulated/0/Android/media/com.github.catfriend1.syncthingandroid[.debug]/” for migration to another release channel of the app.

======== ORIGINAL POST ==============

Description of the issue

all files access switch greyed out when trying to grant files permissions

Reproducer

open a fresh install of syncthing fork and try to grant files permissions

Version Information

App Version: 1.9.0.2
Syncthing Version: v1.9.0
Android Version: Android 11 full release
Device manufacturer: Google
Device model: Pixel 2 G011A

### Device platform info
[ro.product.board]: [walleye]
[ro.product.brand]: [google]
[ro.product.build.date]: [Wed Jul 29 23:26:21 UTC 2020]
[ro.product.build.date.utc]: [1596065181]
[ro.product.build.fingerprint]: [google/walleye/walleye:11/RP1A.200720.009/6720564:user/release-keys]
[ro.product.build.id]: [RP1A.200720.009]
[ro.product.build.tags]: [release-keys]
[ro.product.build.type]: [user]
[ro.product.build.version.incremental]: [6720564]
[ro.product.build.version.release]: [11]
[ro.product.build.version.release_or_codename]: [11]
[ro.product.build.version.sdk]: [30]
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.product.device]: [walleye]
[ro.product.first_api_level]: [26]
[ro.product.locale]: [en-US]
[ro.product.manufacturer]: [Google]
[ro.product.model]: [Pixel 2]
[ro.product.name]: [walleye]
[ro.product.odm.brand]: [google]
[ro.product.odm.device]: [walleye]
[ro.product.odm.manufacturer]: [Google]
[ro.product.odm.model]: [Pixel 2]
[ro.product.odm.name]: [walleye]
[ro.product.product.brand]: [google]
[ro.product.product.device]: [walleye]
[ro.product.product.manufacturer]: [Google]
[ro.product.product.model]: [Pixel 2]
[ro.product.product.name]: [walleye]
[ro.product.system.brand]: [google]
[ro.product.system.device]: [walleye]
[ro.product.system.manufacturer]: [Google]
[ro.product.system.model]: [Pixel 2]
[ro.product.system.name]: [walleye]
[ro.product.system_ext.brand]: [google]
[ro.product.system_ext.device]: [walleye]
[ro.product.system_ext.manufacturer]: [Google]
[ro.product.system_ext.model]: [Pixel 2]
[ro.product.system_ext.name]: [walleye]
[ro.product.vendor.brand]: [google]
[ro.product.vendor.device]: [walleye]
[ro.product.vendor.manufacturer]: [Google]
[ro.product.vendor.model]: [Pixel 2]
[ro.product.vendor.name]: [walleye]

Android Log

android log.txt

[JLJTGR]

Essentially this fork claims it is Android 11 ready, so the OS applies more restrictions on it. The other version doesn’t claim this, so the OS is more lax so it doesn’t crash the app.

Now that Android 11 is out, soon Google will not allow the other app to upload updates without saying it is ready for Android 11, where it will be restricted in the same way.

For frustrating reasons, not updating the other version made it work better.

[Catfriend1]

Interesting, I’ve again removed the fork from the gplay store and told google I’ve quit . Reveived an email today that the fork app got all files access approved , sounding like “hey dev why do you complain so much, we have approved , please come back”. Before that, not a single of my seven reachouts to google support found an open ear. Anyways, the GPlay Release v1.16.0.3 is live now for everybody.