I remember reading somewhere that Android 11 doesn't allow you to access the storage of your phone using Appinventor.
My app is all about taking a photo, and then tweeting / emailing it. It works perfectly on Android 9, but on Android 11, it doesn't attach the image.
My App takes a photo using the Camera Component, Displays it in an image, and then shares it by using the image.picture block. But, as the image.picture also leads to the internal storage, the app doesn't work.
As Android 11 is the newest Android version, many people will be using it, and my app will essentially not work for them. So, is there any way to go around this rule?
Also, I don't think that the problem is anything with the tempComponent variable, as in an earlier version of the App, the when any image.click wasn't there, as it would straightway choose image1.picture in the attachment column
Also see
The problem seems to be with the Android 10 / 11 or maybe because both the Android 10 and 11 are OnePlus phones and the Android 9 is a Samsung phone
Thanks ! I'll just look it up and then if it works; will mark it as solution.
Just curious, shouldn't the path of the picture, by default, be that of how it is saved? Like I am only removing file:// from the path of the image already there, not specifying another path.
So, even if the paths are different, the segment text block should still edit it the same way and give the result respective to what the original path was?
Sorry, the Android 11 Device is my mother's phone, and she was using it, so I couldn't test using it.
Right now, upon testing with the Android 11 Phone, I still wasn't able to figure out how exactly do I solve my problem.
I even tried giving the full file path (/storage/emulated/0/Android/data/edu.mit.appinventor.aicompanion3/files/Pictures/app_inventor_1619777203718.jpg) as an attachment, but it still isn't working.
Even If I use that extension, how exactly do I make it work?
will not be possible anymore after App Inventor targets SDK 30...
you should completely remove that block, because the image will be stored in the ASD anyway...
Hi, I thought of one way in which I might be able to make it work - if I use the Component to Image Extension, and then the output of which I can use in the attachment column of the share block.
Do you think it would work? I will try it, and then get back.