Take picture with camera (error 908)

[Julien_Launay]

Hello, I try to take a picture with the camera in appinventor.
I add askforpermission in screen1 "android.permission.WRITE_EXTERNAL_STORAGE"
But when I start my application I hace error 908 the permission WRITE_EXTERNAL_STORAGE has been denied.
So, do you have a solution please.
Regards.
Julien

[TIMAI2]

See here

(Take image and save to app) camera component still asks for WRITE permission

Good day all, I am working on another app. With this app I have 4 textboxes that get saved to a list with tinydb when the button is pressed. This works. Also, I want to press a button which opens the camera, I take a picture and it gets saved to the tinydb as well as shown on the picture field and when the app is closed and opened at another time, the picture should still be visible at the same spot. So, with the Companion everything works, but when I compile the app the picture taking doesn't…

regarding the bug in the camera component, and possible fixes. You may need to wait until MIT releases the bug fix for a more permanent and google play friendly solution

[Bumble]

On screen1 properties set DefaultFileScope to Legacy.

[Julien_Launay]

Hello,
Thanks, but I just found in red Filescope legacy. So What is the method to use ton connect filescope legacy?
Thanks to be precise.
Thanks to help.
JL

[Taifun]

@Julien_Launay

Thanks, but I just found in red Filescope legacy. So What is the method to use ton connect filescope legacy?

see this example

(Take image and save to app) camera component still asks for WRITE permission

Yes, this is another bug. → @ewpatton cameraSdk30.aia (1.7 KB) The Camera component saves the picture in the ASD for devices with Android > 9. This doesn't require WRITE permission, which by the way is no longer available under Android 11. But as a work-around, the problem can be bypassed if → DefaultFileScope is set to Legacy in the Designer: [grafik] Through this READ and WRITE are declared in the Manifest for all Android versions. WRITE permission for Android 11 actually makes no sense,…

however

@TIMAI2

regarding the bug in the camera component, and possible fixes. You may need to wait until MIT releases the bug fix for a more permanent and google play friendly solution

Taifun

[gordonlu310]

Welcome back,

The same errors were reported in similar topics. In the Screen1 Properties, find the option 'DefaultFileScope'. In the drop down below it, select 'Legacy'.

This is a bug which needs to be fixed.