Speicherzugriffsproblem beim Download des QR-Codes in Android-App

User Message
Für das Downloaden des QR Codes zum Teilen wird der Zugriff auf Speicher nötig. Es kommt eine Entsprechende Fehlermeldung. In Android App Einstellungen gibt es den Reiter Speicher Zulassen oder Medien zulassen aber gar nicht.

Environment Details

• App: Jotform
• Platform: Android
• App Version: 2.12.46
• Device: User Device: samsung - SM-S938B - Handset - 16

Hi Johannes,

Thanks for reaching out to Jotform Support. Our German Support agents are busy helping other Jotform users right now, so I'll try to help you in English using Google Translate, but you can reply in whichever language you feel comfortable using. Or, if you'd rather have support in German, let us know and we can have them do that. But, it might take a while until they're available again.

Now, coming back to your question, downloading the QR code from the Jotform mobile app requires storage access. To resolve the issue, you have to grant storage access from your app settings. You can follow the guide here to learn more about Changing Your App Permissions.

Reach out again if there’s anything else we can help you with.

Vielen Dank für Ihre Antwort.
Das Problem ist, ich habe in den Einstellungen gar nicht die Option Zugriff
auf den Speicher oder etwas vergleichbares zu geben.
Auf den Bildern sehen sie die Fehlermeldung und die mögliche Auswahl der
App Berechtigungen.
Jotform <noreply> schrieb am Mi., 28. Jan. 2026, 18:01:
</noreply>...

Hi Johannes,

It looks like that your image/screenshot did not get through and I can not see it. You can use Loom or upload to Google Drive or Dropbox, then send us the link. We’ve also got a guide explaining how to send us a screenshot.

When we hear back from you, we’ll be ready to move forward.

https://www.dropbox.com/scl/fo/zc1f77hbo8p6q19v0ntqg/AP3lteSZjdx12mvRXm0BxI8?rlkey=d77n868l82314igi9ba7a144g&st=g027squn&dl=0
Jotform <noreply> schrieb am Mi., 28. Jan. 2026, 19:54:
</noreply>...

Hi johanneseichberger1,

I tested your form and had the same issue, so I created a ticket and escalated this to our Developers. Although we don't know exactly when it'll be fixed, we’ll circle back to this thread when we have an update.