Error Sorry Sample.General

Submitted by ANZAC on

1. App Name (which app are you using)

iRecord App

2. Issue Description (clearly explain the problem you’re experiencing) 

I receive a red boxed error message, as per the attached screenshot, every time I try to upload individual OR all completed records. The error starts off "Sorry Sample.General"

3. Expected Behaviour (what did you expect to happen instead)

I expect to be able to upload all the completed records as per usual.

4. Steps to Reproduce (list the steps someone can follow to see the issue)

1. Open the iRecord app 2. Navigate to the Home tab 3. Press the Upload All button 4. Error occurs.

Or

1. Open the iRecord app 2. Navigate to the Home tab 3. Press any one of the four completed records. 4. Press Upload button 5. Error occurs.

5. Date/Time Issue Observed (when did you first notice the issue, provide a specific date if possible)

Today 24/7/2026 every time since 1230 hours GMT

6. Frequency of the Issue (is it consistent or intermittent)

Every time I have tried today since 1230 hours GMT. Even AFTER I have: I have restarted the phone. I have cleared the iRecord cache and restarted the phone again. Error still occuring afterwards.

7. Screenshots or Screen Recording (optional – helps illustrate the issue clearly)

 https://ibb.co/9khTL2XN

8. App Version (which version of the app are you using, check in the app settings or app store)

V6.3.4 (288)

9. Device (what phone or tablet are you using, include model and brand

Google Pixel Pro 9 XL

10. Operating System Version (The Android or iOS version running on your device)

 Android 17 Build Number: CP2A.260705.006

11. System Update Status (are any pending Android/iOS updates)

No. The entire phone is up to date.

 

 

Clearing storage didn't help either.

 

8 hours later and everything is now WORKING AGAIN; my conclusion is that the problem was NOT at my end but at the server end...

Comments

Submitted by karolis on Wed, 29/07/2026 - 16:16

Permalink

Thank you for filling in the issue form with the details. Yes, that screenshot tells me this was a temporary server issue. Let me know if this happens again.