Image does not appear when using the image picker in the apk

Discuss
1

In this thread, resolved by our colleagues: What is the best image selector? - #40 by Taifun
I encountered the following issue. When I use the companion to select an image from the gallery, it appears and saves to Cloudinary. When I do this via the APK, the screen goes black, freezes, and nothing appears, not even the “Wait” or “Close app” messages.
For photos, I can take, display, and send them to Cloudinary via the companion or the APK.
See the steps below.

This code block is a visual programming script that shows a radio list dialog with options to either take a photo or select an image when the "btn_tirar_foto" button is clicked, including buttons to confirm or cancel the action. (Captioned by AI)
This code block is a visual programming script that shows a radio list dialog with options to either take a photo or select an image when the "btn_tirar_foto" button is clicked, including buttons to confirm or cancel the action. (Captioned by AI)674×324 18.6 KB

This image shows a block-based programming code snippet that handles radio button selection to either take a picture with the camera or select an image from the device, including visibility toggles and image rotation settings. (Captioned by AI)
This image shows a block-based programming code snippet that handles radio button selection to either take a picture with the camera or select an image from the device, including visibility toggles and image rotation settings. (Captioned by AI)602×424 35.4 KB

This image shows a visual block-based programming interface where a series of blocks are used to upload a picture from an activity result to Cloudinary with specified format and folder settings. (Captioned by AI)
This image shows a visual block-based programming interface where a series of blocks are used to upload a picture from an activity result to Cloudinary with specified format and folder settings. (Captioned by AI)908×420 36 KB

A visual programming code block designed to handle errors, access a pictures directory, process image paths, and upload a .png image with specific tags using Cloudinary. (Captioned by AI)
A visual programming code block designed to handle errors, access a pictures directory, process image paths, and upload a .png image with specific tags using Cloudinary. (Captioned by AI)957×612 53.6 KB

blocks(25)
blocks(25)386×115 6.07 KB

A mobile phone screen displays a black background with the time 18:01 shown in the top left corner, along with various status icons at the top including battery, signal, and notifications. (Captioned by AI)
A mobile phone screen displays a black background with the time 18:01 shown in the top left corner, along with various status icons at the top including battery, signal, and notifications. (Captioned by AI)280×603 3.47 KB

I used android.intent.action.GET_CONTENT instead of android.intent.action.PICK. In this one, the image appears, but it doesn’t send the photo to Cloudinary, and a message appears asking if I want to wait or close the app. This is all in the apk.

If anyone wants to test it, follow the aia.
imagens.aia (409.7 KB)

2

Use logcat to find out what’s going on

Taifun

3

Have you requested permission to access the files in the shared folders?

eb0c6466cb7ae87795ca6fcd02d70ff47424d9a1
eb0c6466cb7ae87795ca6fcd02d70ff47424d9a11920×1018 118 KB

4

It says the image is loading! The problem is that the app freezes during the process.

1 Like
5

A code snippet from a visual programming environment that sets an activity to get image content using an intent, and then retrieves the content URI, filename, and path from the URI. (Captioned by AI)
A code snippet from a visual programming environment that sets an activity to get image content using an intent, and then retrieves the content URI, filename, and path from the URI. (Captioned by AI)696×187 11.9 KB

Unfortunately, Kodular and the Cloudinary component lack a block to report loading errors.
Use screen1.errorOccurred without a conditional and see if it gives you anything.

6

I used screen1.errorOccurred just to see the error message, and here it is when I launched the app. This is before I even selected the image.

A mobile app screen titled "Screen1" showing a button labeled "Tirar foto," a message about denied WRITE_EXTERNAL_STORAGE permission, a number "908," and two input boxes with hints "Hint for Text_Box1" and "Hint for Text_Box2." (Captioned by AI)
A mobile app screen titled "Screen1" showing a button labeled "Tirar foto," a message about denied WRITE_EXTERNAL_STORAGE permission, a number "908," and two input boxes with hints "Hint for Text_Box1" and "Hint for Text_Box2." (Captioned by AI)302×539 13.7 KB

I saw a post about this permission issue and the solution. Would this work for me?

7

The extension he is using has a block to catch errors.

Your application shouldn’t require write permissions,

Does that error appear without clicking anything?

8

I did as per the video but it didn’t help at all. This error only occurs on Android >10

9

immagine
immagine703×126 6.52 KB

I think the error comes from this component

10

I didn’t have any problems here. Kodular does give permissions errors. Stop messing with Kodular.
Android 15

The image shows a colourful block-based visual programming interface with multiple connected code blocks for camera permissions, image capture, and uploading an image to an online service. (Captioned by AI)
The image shows a colourful block-based visual programming interface with multiple connected code blocks for camera permissions, image capture, and uploading an image to an online service. (Captioned by AI)677×859 108 KB

11

I’ll respond to both of you, Gianluca and Gaston.
Gianluca, I’m not using the Image Editor component.
Gaston, the Initialize and Permission Granted blocks:
In this IsPermissionGranted Permission condition, you used Niotron. In Kodular, would it be Are Permissions Granted?
Another thing, was this test you ran on the companion or the APK?
According to you, I said to stop messing with Android 15. What did you mean by that?
I’ve seen apps on the Play Store stating that they only support Android up to, for example, 11. Is there a way to limit this?

The image shows a block-based programming interface with two code sections that check and request permission to read media images when Screen1 initializes and when permissions are granted. (Captioned by AI)
The image shows a block-based programming interface with two code sections that check and request permission to read media images when Screen1 initializes and when permissions are granted. (Captioned by AI)733×447 21.6 KB

12

Yes :grin:

immagine
immagine234×744 19.8 KB

13

Even if he’s not used in the blocks just because he’s on the influence list? Honestly, I didn’t know that. :grinning_face_with_smiling_eyes:

1 Like
14

I removed the image editor from the project, compiled the APK, and although the message no longer appears, I still get the same error. When I click on the image in the photo gallery, it freezes for a while and then the screen goes dark.

I’ll test it on another device with Android 9.

15

Try this, if you haven’t already, and let me know.
blocks

blocks(1)
blocks(1)940×458 35 KB

1 Like
16

Gianluca, you’re the man!
It worked! Awesome!
We can finish as resolved

1 Like
17

Even if you’ve already solved the problem and the answer to @RaYzZz is the same as the one I gave you before, good for that.

It always compiles on the highest API version, what you can limit is which one onwards.
Nio*tron allows you to choose both parameters, but kodular does not.

18

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.