No Matches Found!
Try with a different search term
we have some ck65 honeywell devices that I open an local htm file within soti surf
file:///sdcard/Download/example.htm
now I have a ct45 honeywell with android 11 and can't open the file on local sd card
"the webpage not available" could not be loaded because: net::ERR_ACCESS_DENIED
soti version: 15.01.1181
soti agent: v15.2
Thanks for the article
I ran request_appops_permission MANAGE_EXTERNAL_STORAGE on the ct45 honeywell which is supposed to allow permissions to the sdcard\download folder but it didn't
I'm running the latest plugin and latest agent
this is weird because because I have a file sync run which places and updates the htm file I'm trying to open, which seems that would be broke also but it's not, the command above was run just a minute ago but that file has been updating since this morning
I will continue to pore over that doc for some other solutions
Can you think of any other place I can put that file
I'm also running the latest plugin 1.19.118
the doc says do one of these things, run the script or update the plugin which "should" give access to the download folder but surf still throwing err access denied
can surf access a public storage space such as the root of sdcard, I dropped an htm file there but also said access denied
newer version of surf didn't work
how can i get soti surf to "access all files" instead of only "allow access to media only"??
another poster said they installed
It works with 15.40 Build 5 of soti surf
I can confirm this works, although I hate to go backwards, it works on Android 11 with soti surf 15.40 build 5
the latest soti download didn't fix the issue which I would have expected v15.6.07
In order to have external storage access on Android 11 an app needs to request the MANAGE_EXTERNAL_STORAGE permission. Apps that are hosted in the public Google Play Store are not allowed to have this permission declared in their manifest, effectively banning its use for any public apps. SOTI Surf is hosted in the public Play Store and it therefore has to follow these rules enforced by Google. This is very likely why the older version of the app works, as it is likely targeting and older Android API level than what is now being enforced as required in Google Play. If you want to blame someone for all of this mess, look no further than Google. This is not SOTI's fault, all enterprise apps that leverage external storage for logging, config, etc, have been affected by this change.
Hey Matt,
thanks for all of your help
I was going off of another poster in soti forum that had called soti, he had reported that soti was going to fix this in a future release of surf, that's why I made the comment about the latest surf didn't fix this
we support soti and they have been great to work with and yes I now understand a little more about these issues
take care
