mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #174] Error during backup/restore: Temporary Gmail IMAP error, try again later. #145
Labels
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#145
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tonya on GitHub (Aug 21, 2011).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/174
I get this error all the time whenever I try to backup my messages. I have not fiddled with the IMAP server settings, and IMAP access is enabled in my Gmail account. I managed to backup about 70 out of 500+ SMS a while back over several tries, but it has not worked since. None of my MMS were backed up.
@drkvogel commented on GitHub (Jan 2, 2012):
bump
@pamfu commented on GitHub (Jan 12, 2012):
Hi! I too get this issue when ever I try to backup through WiFi! On the same WiFi, SMS Backup+ works initially without any problem. Then, after a some time, in my case a few days, this error starts popping up. I need to switch to my mobile carrier to ensure backup.
@drbubba commented on GitHub (Jan 18, 2012):
Same here. Been unable to back anything up since the 17th.
@jsleroy commented on GitHub (Jan 20, 2012):
Same here. I managed to get it working by disabling the Wifi connection.
@jberkel commented on GitHub (Jan 20, 2012):
@drbubba @jsleroy @pamfu @drkvogel Android version / phone ?
@jsleroy commented on GitHub (Jan 20, 2012):
Android 2.2.1 / HTC wildfire
@pamfu commented on GitHub (Jan 21, 2012):
Android 2.3 / HTC Desire
Now, Android 4.0.1 / HTC Desire
@craigmb24 commented on GitHub (Jan 24, 2012):
Same here, disabling wifi worked for me also.
Android 4.0.2 / Galaxy Nexus
@TTLucian commented on GitHub (Jun 15, 2012):
Same here. Galaxy S2 ICS 4.0.3. First manual backup only worked on 3G connection, after disabling wifi. Sometimes I got IMAP error and other times I got IO error.
@BurntSushi commented on GitHub (Aug 9, 2012):
I can also confirm that I had this issue, and disabling wifi seems to have solved the problem.
Android 4.0.4 / Galaxy Nexus / Verizon
@DaleEMoore commented on GitHub (Nov 15, 2012):
Has anyone found a resolution to this problem?
@iMilnb commented on GitHub (Nov 18, 2012):
Same error, same "fix", SMS Backup+ seems to fail when working over WiFi.
@pR0Ps commented on GitHub (Nov 23, 2012):
Same issue. Fails over WiFi, works over data connection. Tried with both XOAuth and plaintext.
HTC Desire C, Andriod 4.0.3
EDIT: Works perfectly on a different WiFi connection. The first connection had some custom proxy settings which was probably the issue.
@bompstable commented on GitHub (Jan 14, 2013):
I'm also having this problem. I have a Google Apps account with Two Factor Auth enabled. I'm connecting using the default IMAP server settings. The first time I connect my account, SMS Backup+ connects and backs up okay. It then manages for the next few attempts (I'm running frequent manual backups in batches of 100). However, after a few more backups it fails to connect. This generally occurs within half an hour of the first successful connection. When it does, the connection spends a long time saying "logging in..." then eventually says "general error: temporary Gmail IMAP error, try again later.". All subsequent connection attempts fail after this - including several hours later.
This occurs on both Wifi and 3g and changing from one to the other does not fix this. The only temporary fix for me is to disconnect and reconnect my account by unticking and reticking the Connect tick box. The app then connects fine straight away, but after a few backups again gets stuck.
I wonder if this is to do with the fact that I use two factor auth on my Google Apps account? Do others having this problem also use it?
@jberkel commented on GitHub (Jan 14, 2013):
is this with version 1.4.7?
@bompstable commented on GitHub (Jan 14, 2013):
Yes, 1.4.7 running on a Nexus 4, Android 4.2.1.
@jberkel commented on GitHub (Jan 14, 2013):
ok, i guess what's happening is that the token expires after a while. i can send you a debug builld you can install to verify this. token expiration is not documented AFAIK. the tokens returned from the browser based log-in don't seem to expire that quickly.
@bompstable commented on GitHub (Jan 14, 2013):
That sounds plausible. Happy to run a debug build if that helps.
For now I've generated an app specific password for SMS Backup+ and set it
to use that instead. I'll report back on whether that cures things. So far
so good.
On 14 Jan 2013 12:33, "Jan Berkel" notifications@github.com wrote:
@jberkel commented on GitHub (Jan 14, 2013):
hm, why do you need a password? does the automatic login does not work?
@bompstable commented on GitHub (Jan 14, 2013):
The automatic login works fine at first, but after a while stops working -
as described above. I've only just started using the app-specific password
in order to try and workaround the problems. By using a password, I'm
hoping that problems related to the token such as it expiring will be
bypassed.
On 14 January 2013 12:40, Jan Berkel notifications@github.com wrote:
@bompstable commented on GitHub (Jan 14, 2013):
Using an app-specific password in place of the automatic login seems to have solved this for me - I was able to finish backing up my existing text messages for the first time. So it looks like it is a problem with the token and possibly related to my use of two factor auth.
I'm happy to help debug this further if needed.
@bompstable commented on GitHub (Jan 16, 2013):
A colleague using a non-apps Google account with two factor auth is having the same problems with 1.4.7. It worked when he initially connected but has silently stopped working since then. Now when he runs a manual backup it sticks on the logging in phase.
Googling suggests that you have to recreate the XOAUTH value for each new connection. http://stackoverflow.com/questions/3078921/imap-oauth-token-expiry
@sshaikh commented on GitHub (Jan 16, 2013):
Same issue here:
4.2.1, nexus 4. Doesn't log in on wifi or network data, but will work if I clear down the auth and retick the box. Will try OTP passwords now. Oh and I also use 2-step.
@iTeedee commented on GitHub (Jan 16, 2013):
I'm getting this error now. Just upgraded my phone from Galaxy S2 to Galaxy S2 HD LTE. Did the restore perfectly, but now getting the "gmail temporary IMAP error" when trying to do the backups on the new phone.
@Ltningbgs commented on GitHub (Jan 17, 2013):
I am having the same issue. I'm not using two factor auth. The issue seemed to start after the last update. If i unconnected and connect again it will initially back up but will not back up anymore after the initial run. I've been using the app for a number of years witout issue. Runing 1.4.7 on a Motorola tonic android version 4.0.4. Feeling lost without this app.
@sshaikh commented on GitHub (Jan 17, 2013):
I wouldn't even mind resetting AUTH if it didn't mean the sync date being reset too. Any way you can remove this dependency too?
@jberkel commented on GitHub (Jan 17, 2013):
looks like the access token doesn't get properly refreshed. will release 1.4.8 soon.
@iTeedee commented on GitHub (Jan 17, 2013):
Wonderful! I'm so excited and waiting. My original phone (Samsung Galaxy S2) was dying so I used your software to back it up. Received my warranty replacement phone (Samsung Galaxy S2 HD LTE) 2 weeks ago and restored everything fabulously!!
But I have not been able to back up current and new data from the new phone after restoring all my data. Found out today they shouldn't have shipped me that phone and I now have a Samsung Galaxy S3 which is my proper warranty replacement phone I should have received. Now I can't activate my new phone (S3) until I can get the new data off the phone I currently have (S2 HD LTE), backed up!
So I'm watching daily for the update to fix this. I have a fixed time period to return this phone before I'll get charged for keeping it!
Good luck!
@sshaikh commented on GitHub (Jan 17, 2013):
In the meantime you can use this to transfer your SMS's offline:
https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore
@casiwito commented on GitHub (Jan 17, 2013):
Bump... running into the same issue reagrdless of using 3G or WiFi networks (tried 4 different ones). I get passed 1000 items on my initial backup and it dies. I've tried this several times including reinstalls/reboots/2nd auth, no go either way. Looking forward to 1.4.8!!! (Huawei Mercury M886 running 2.3.6 on Cricket Wireless)
@jberkel commented on GitHub (Jan 17, 2013):
@casiwito @iTeedee @Ltningbgs can you guys try 1.4.8-BETA1 ?
https://www.dropbox.com/s/i2jk68ualhlicms/sms-backup-plus-1.4.8-BETA1.apk
let me know if it fixes the problem.
@casiwito commented on GitHub (Jan 17, 2013):
For some reason this last attempt today is working. I have 3450 of 4164
initial items backed up so far... i will test after this finishes
(successfully or not)
Thanks for getting this new build out, I'll keep you posted
-Paul.
On Thu, Jan 17, 2013 at 3:46 PM, Jan Berkel notifications@github.comwrote:
@Ltningbgs commented on GitHub (Jan 17, 2013):
Bata already installed. Was able to do a manual back up of messages received since last time reinstalled. Waiting to see if autiback up will work & will post later
@casiwito commented on GitHub (Jan 17, 2013):
So my initial backup failed at 3664 out of 4164 total items. I tried
backing up twice using 1.4.7 and it failed every time. I then download and
installed the 1.4.8 beta APK and it replaced the 1.4.7 app. After
installation I initiated a manual backup once again and it has started to
backup the remaining 500 items. Its on item 102 and I'm optimistic. Will
keep you posted.
-Paul
On Thu, Jan 17, 2013 at 4:00 PM, Paul Lago casiwito@gmail.com wrote:
@casiwito commented on GitHub (Jan 17, 2013):
1.4.8 was installed over 1.4.7 and was able to complete backing up the
remaining 500 items which 1.4.7 would not do. All my items are now backed
up and I'm thrilled. Nice job and thank you!!!
-Paul
On Thu, Jan 17, 2013 at 4:16 PM, Ltningbgs notifications@github.com wrote:
@sshaikh commented on GitHub (Jan 17, 2013):
Manual sync worked perfectly. Thanks for the quick fix!
@Ltningbgs commented on GitHub (Jan 18, 2013):
Auto back up is working perfect! Thanks for the fast work in coming up with a solution to fix the problem!
@EstebanForge commented on GitHub (Jan 18, 2013):
Came here to say i was having the same problem.
1.4.8 BETA1 solved the problem.
Thanks for the fix!
@iTeedee commented on GitHub (Jan 18, 2013):
It's working! OMG, I'm so excited! At #59 of 21,412. Will let it run overnight to see if i get everything. Will post tomorrow. Will it pick up where it left off if it doesnr complete overnight?
@iTeedee commented on GitHub (Jan 18, 2013):
Got through 10,000 last night. I'll get the other 11,000 tonight! Can't wait, then I can send this phone back and move to my new phone! A donation is coming at you. The speedy response with a solution and the grief you have saved me is well worth it. I hope everyone else with this problem that you've now solved will hit the donate button with me!
@casiwito commented on GitHub (Jan 18, 2013):
Agreed. Donation is on its way!
On Jan 18, 2013 5:23 AM, "iTeedee" notifications@github.com wrote:
@alexjohnson505 commented on GitHub (Jan 18, 2013):
Experienced the same issue.
Turning off Google's two-step authentication, disabling wifi, then logging back into the app reset the counter, but allowed me to run a complete backup again.
@jberkel commented on GitHub (Jan 18, 2013):
ok, thanks for beta testing. releasing this as 1.4.8 to google play store now.
@Gilesy commented on GitHub (Jan 20, 2013):
Great! All working again now. Thank you.
@christophgysin commented on GitHub (Jan 21, 2013):
I'm having the same issue since the beginning of the year. Installed 1.4.8 just now, but the problem still persists. Tried to disconnect and connect again with the stored gmail account. Moved the app to phone storage. Even rebooted the phone.
This is on Android 4.0.4 on SonyEricsson LT18i
@Libel commented on GitHub (Jan 28, 2013):
Same problem .. Sony Experia J
Installed 1.4.8, but problem still persist. I tried to backup sms on a diffrent gmail acount, still nothing.
Logging in ..
@ashrutkhatter commented on GitHub (Mar 22, 2013):
Selected this app due to good positive feedback on Google Play. But i am stuck with the same error, and after trying out everything suggested I still keep getting the same error
@uditch commented on GitHub (Apr 1, 2013):
This error is still persisting in the update app. The backup only works when wifi is disabled and it is performed over on network data.
App version: 1.4.8
Android Version: 4.2.2
Device: LG/Google Nexus 4
@emerich commented on GitHub (Apr 11, 2013):
I have the same issue with Sony Xperia Tipo Dual Sim : I uninstalled then reinstalled SMS Backup + and it works fine now. It may be that activating Wifi AND Data Connection (GPRS/EDGE/3G) seems to cause the problem also, but not sure.
Anyway, this app is awesome. Thanks a lot.
@sanelson2000 commented on GitHub (May 31, 2013):
I'm having the same issue with the latest version (which claims to fix this error in the description) with the Galaxy S4 on Verizon. If WiFi is enabled I get the IMAP error. If I turn WiFi off it seems to work fine. It worked fine on my old phone (Motorola Droid Bionic).
I tried manually setting the IMAP settings, but it still persists.
Some details:
GMail: Standard @gmail.com account, using 2 step authentication.
Network: Verizon 4G LTE / CDMA (although it usually tends to be in 3G when I'm at home).
WiFi: ASUS RT-N66U running DD-WRT, Connected on the Wireless N - 5Ghz spectrum.
Phone: Samsung Galaxy S4 (SCH-I545)
Android: 4.2.2
And, thanks for the app. It's great when it works!
@jberkel commented on GitHub (Jun 30, 2013):
looks like this is a phone specific bug.
@adrian-vg commented on GitHub (Mar 29, 2018):
This is still a problem. While on wifi I get the error, when not, it seems to work.
Running SMS Backup+ v1.5.10 on a Oneplus One. Had the same problem on my previous Galaxy 2 and 3. Does not seem to be a problem on my Nexus 6P.
@jberkel commented on GitHub (Mar 29, 2018):
@adrian-vg Can you try again with the latest beta?
See https://github.com/jberkel/sms-backup-plus#beta-testing
@adrian-vg commented on GitHub (Mar 29, 2018):
Seems to be working.
Thanks!
Is it still that token-problem mentioned earlier, or something else?
@adrian-vg commented on GitHub (Mar 29, 2018):
It’s strange though that only the last four test texts are backed up. The other 2000+ texts and almost 200 calls are not.
@jberkel commented on GitHub (Mar 29, 2018):
@adrian-vg not sure why what would be. maybe reset the backup state? (Select "Reset" from the menu)
@adrian-vg commented on GitHub (Mar 29, 2018):
Will try, thanks.
Edit: That did it. Thanks again!
Edit2: And I realised I forgot to check the backup call log. It works now.