Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Problem Retrieving Data" and then crash #5811

Open
3 tasks done
stefan2904 opened this issue May 20, 2024 · 7 comments
Open
3 tasks done

"Problem Retrieving Data" and then crash #5811

stefan2904 opened this issue May 20, 2024 · 7 comments

Comments

@stefan2904
Copy link

stefan2904 commented May 20, 2024

  • I have searched open and closed issues for duplicates (this is similar but just in a comment; Crash on Launch (Launch Failure) #5395 (comment))
  • I am submitting a bug report for existing functionality that does not work as intended
  • This isn't a feature request or a discussion topic

Bug description

When I start Signal, I get the "Problem Retrieving Data" screen. After confirming it, the all displays that it is now recovering the database but crashes after 10 seconds. There is no way to skip the recovery or retrieve debug logs.

It might be the case that this was triggered by a full device storage, but now there is >1GB space free.

Steps to reproduce

  • Start app
  • Immediately get "Problem Retrieving Data" screen
  • Click continue
  • For 10 seconds, get recovery screen

Actual result: Describe here what happens after you run the steps above (i.e. the buggy behaviour)

  • App crashes without Error message or debug log
  • No access to existing or new messages, not able to send messages

Expected result: Describe here what should happen after you run the steps above (i.e. what would be the correct behaviour)

  • Successful Recovery
  • Able to start Signal and access messages

Screenshots

IMG_20240520_105620_451

IMG_20240520_105616_814

Device info

Device: iPhone SE 2020

iOS version: 17.3.1

Signal version: 7.11

Link to debug log

  • Log from app not available
  • Log from iOS send to signal support.
@stefan2904
Copy link
Author

stefan2904 commented May 20, 2024

The log indicates a SIGTRAP and some Address size faults below.

{"beforePC":"4gMZquMDF6rkAxWq5QMTquYDFqrnAxiqFQCA0pUDAJTgAxSq1xgPlA==","atPC":"IAAg1IgSgFL\/EwC56AcA+UgAgFLoAwA54CYAsADQLZHjJgCwY0A6kQ=="},
  "basebandVersion" : "5.00.00",
  "exception" : {"codes":"0x0000000000000001, 0x00000001a96fe3fc","rawCodes":[1,7137649660],"type":"EXC_BREAKPOINT","signal":"SIGTRAP"},
  "termination" : {"flags":0,"code":5,"namespace":"SIGNAL","indicator":"Trace\/BPT trap: 5","byProc":"exc handler","byPid":1265},
  "os_fault" : {"process":"Signal"},
  "faultingThread" : 2,
  "threads" : [{"id":115944,"threadState":{"x":[{"value":268451845},{"value":21592279046},{"value":8589934592},{"value":40694815129600},{"value":0},{"value":40694815129600},{"value":2},{"value":4294967295},{"value":18446744073709550527},{"value":9475},{"value":0},{"value":1},{"value":9475},{"value":11257864},{"value":4398046511104},{"value":0},{"value":18446744073709551569},{"value":7385227492,"symbolLocation":56,"symbol":"clock_gettime"},{"value":0},{"value":4294967295},{"value":2},{"value":40694815129600},{"value":0},{"value":40694815129600},{"value":6132049800},{"value":8589934592},{"value":21592279046},{"value":21592279046},{"value":4412409862}],"flavor":"ARM_THREAD_STATE64","lr":{"value":8449691408},"cpsr":{"value":0},"fp":{"value":6132049648},"sp":{"value":6132049568},"esr":{"value":1442840704,"description":" Address size fault"},"pc":{"value":8449692024},"far":{"value":0}},"queue":"com.apple.main-thread","frames":[{"imageOffset":4472,"symbol":"mach_msg2_trap","symbolLocation":8,"imageIndex":26},{"imageOffset":3856,"symbol":"mach_msg2_internal","symbolLocation":80,"imageIndex":26},{"imageOffset":3624,"symbol":"mach_msg_overwrite","symbolLocation":436,"imageIndex":26},{"imageOffset":3176,"symbol":"mach_msg","symbolLocation":24,"imageIndex":26},{"imageOffset":219804,"symbol":"__CFRunLoopServiceMachPort","symbolLocation":160,"imageIndex":27},{"imageOffset":211348,"symbol":"__CFRunLoopRun","symbolLocation":1208,"imageIndex":27},{"imageOffset":209912,"symbol":"CFRunLoopRunSpecific","symbolLocation":608,"imageIndex":27},{"imageOffset":13560,"symbol":"GSEventRunModal","symbolLocation":164,"imageIndex":28},{"imageOffset":2279584,"symbol":"-[UIApplication _run]","symbolLocation":888,"imageIndex":29},{"imageOffset":2277084,"symbol":"UIApplicationMain","symbolLocation":340,"imageIndex":29},{"imageOffset":4547992,"imageIndex":29},{"imageOffset":176700,"imageIndex":25},{"imageOffset":24012,"symbol":"start","symbolLocation":2240,"imageIndex":30}]}
...

@stefan2904
Copy link
Author

stefan2904 commented May 21, 2024

fyi, the Signal support team replied to my email that they are aware of and working on that issue, but they cannot give a timeline.

So, in my case, I had to reset the app, loosing all old messages. 😭

@acanis
Copy link

acanis commented May 22, 2024

This exact same issue just happened to me. My iPhone was running out of space and I opened signal. Now after freeing up space the Signal app says "Problem Retrieving Data" and immediately crashes when I click continue.
Is there no way to recover the data?

@birfan
Copy link

birfan commented May 24, 2024

Tap 8 times on the white area of "Problem Retrieving Data". It will ask "What would you like to do with the link to your debug log?", and choose email support. I sent a bug report for the same issue last week.

I just hope they will fix it soon. The more people send their report, the more they will (hopefully) pay attention to this bug. Last two updates haven't fixed it for me, and I have read every single post about this issue. There is no way to recover the data.

@Nerodelo
Copy link

I got the same issue, any update? I don't want to lose my data

@Nerodelo
Copy link

Tap 8 times on the white area of "Problem Retrieving Data". It will ask "What would you like to do with the link to your debug log?", and choose email support. I sent a bug report for the same issue last week.

I just hope they will fix it soon. The more people send their report, the more they will (hopefully) pay attention to this bug. Last two updates haven't fixed it for me, and I have read every single post about this issue. There is no way to recover the data.

It's impossible for me to send report, app crash before

@birfan
Copy link

birfan commented Jun 2, 2024

Tap 8 times on the white area of "Problem Retrieving Data". It will ask "What would you like to do with the link to your debug log?", and choose email support. I sent a bug report for the same issue last week.
I just hope they will fix it soon. The more people send their report, the more they will (hopefully) pay attention to this bug. Last two updates haven't fixed it for me, and I have read every single post about this issue. There is no way to recover the data.

It's impossible for me to send report, app crash before

Don't click "continue" on the "problem retrieving data" screen. Just tap 8 times on the white area. If that doesn't work, try contacting support directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants
@acanis @stefan2904 @birfan @Nerodelo and others