Issue with Scan Storage setting in Android 13

Question

Hello, 
 
 I'm using Intercept X for Mobile on a Nokia C32 running Android 13 and I could no longer turn on the Scan storage setting. 
 I always had Settings > Targets > Scan storage in the On state but I accidentally tapped it while trying to scroll up. I tried to tap it again to turn it back on but now it won't turn on. There's a small tool tip text saying, "You need to allow this permission in order to use..." I revisited the app permissions and can confirm that all permissions are allowed for Intercept X. 
 I'm not sure what's going on here but I have a theory. I noticed that in Android 13, the Storage permission is no longer there. Instead, it appears to have been replaced and split into two separate permissions: Photos and videos, and Music and audio. Unfortunately, neither of those two are in the list of permissions for Intercept X so I suspect that might be the cause of the issue. 
 Kindly take note of the following details: 
 
 Nokia C32, Android 13, Build number 00WW_1_260 
 Intercept X version 9.7.3559 
 
 This is annoying, makes me feel unsafe. Please help.

hot head · Answer

This is disturbing. Although I am relieved that uninstalling then reinstalling fixed the problem, I find it ridiculous that this is the fix for accidentally turning off a single setting. 
 I did some research on my theory and apparently I am right: Storage permission (which is READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE) is being deprecated. You may refer to official Android release information here: 
 https://developer.android.com/about/versions/13/behavior-changes-13 
 So in my mind (and I'm hoping others in this forum think the same), your developers have some work to do. 
 First, you need to update the permissions being targeted by Intercept X and adapt it to the new granular permissions provided in Android 13 and later. Doing this will help avoid the need of uninstalling then reinstalling the app (then reconfiguring it back to the way it was) which is a waste of time. 
 Second, you may want to do a small change in the way users could trigger a manual update. The reason why I ended up in this accident is because I wanted to manually check if there are more recent AV signatures. To do that, users have to go into Settings then scroll to tap the Last update field under Sophos Anti-Virus engine section just to trigger that manually. Unfortunately for me, I accidentally tapped something else and there I was with a supposed-to-be-uncomplicated problem. Now that same thing is actually visible under Dashboard > App security. But it's basically just a read-only version of what you see in Settings. No matter how many times you tap the Last engine update field, it won't trigger a manual signature update. 
 So maybe you would like to consider making that change? For 2 reasons I am suggesting this: (1) a shortcut instead of having to go into Settings and ending up with accidents like this and (2) I believe the Settings page would generally be locked down by the IT department for enterprise end-users, so how can people trigger a manual signature update (if they want to for whatever reason) if they can't get to that screen to do so? 
 Can you do me a favor and pass this on to the coding folks? I really find it crazy that I have to uninstall and reinstall when the resolution should have been just tap the setting again to turn it back on.