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
Crashes lately #131
Comments
At the time of my crash, the first time download had been running for 1
hour. It felt like a timeout. When I re-launched and resumed, it felt like
another 2 hours was needed to fully download the current set of images.
…On Tue, Oct 2, 2018 at 11:20 AM Christopher Prince ***@***.***> wrote:
1. Rod-- when he was zooming in on an image
2. Dany-- when he was downloading images when the app was installed on
a new device
3. Natasha-- IIRC, when she was looking at the discussion for an image.
Need to upload the dSyms's for the app to Crashlytics and get the crash
reports.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#131>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJEDwgko1vJEkd61Cjim50Ji3zGq6dYDks5ug4QfgaJpZM4XERJi>
.
|
On Dany's issue-- looking at the logs, I found crspybits/SyncServerII#89. Dany suggests "Seems to me that the si crash was some aggregated by the slow download. Possibly some sort of unhandled timeout?". |
Possibly, the app went into the background on Dany's downloads because the screen locked? I have to check, but I think apps do go into the background when the screen locks. SharedImages really needs to be handling background downloads better. See https://stackoverflow.com/questions/29029632/is-an-ios-app-active-when-the-device-is-locked and https://developer.apple.com/library/archive/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/StrategiesforHandlingAppStateTransitions/StrategiesforHandlingAppStateTransitions.html |
On Dany's issue -- first time download: There are a few issues with first time download. I think the main one is that the app shouldn't crash. I've got a ticket for that. |
Dany: Here are my concerns over that issue : your server should not be absorbing all that bandwidth. You will incur heavy usage carges everytime a customer initializes a new device. |
Symbol was not "network not available". It was the nothing to download.
Working as designed.
…On Wed, Oct 17, 2018 at 10:33 AM Christopher Prince < ***@***.***> wrote:
Another from Dany:
Getting the network not available symbol when trying to refresh “shared
images”.
I tried restarting the app.
How I got in this situation was to start a refresh last night (new
version) and then close the iPad. This morning I tried to continue it, but
it kept not progressing.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#131 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJEDwq9dign-_FIWR1XBG423nPztPQN9ks5ulz_RgaJpZM4XERJi>
.
|
The crashes look like they should be from v0.19.0 of the app. However, when I upload the dSyms for this, I get no crashes reported with Crashlytics. Yarg. |
Don't have enough info to take this further. |
Need to upload the dSyms's for the app to Crashlytics and get the crash reports.
The text was updated successfully, but these errors were encountered: