[GH-ISSUE #554] Gmail doesn't support XOAUTH anymore #469

New issue

Closed

opened 2026-02-26 01:30:40 +03:00 by kerem · 34 comments

kerem commented 2026-02-26 01:30:40 +03:00

Owner

Copy link

Originally created by @mtomana on GitHub (May 7, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/554

"Server does not support XOAUTH".
Google turned off XOAUTH. Only XOAUTH2 is now supported.
Detailt: https://developers.google.com/gmail/xoauth_migration

Originally created by @mtomana on GitHub (May 7, 2015). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/554 "Server does not support XOAUTH". Google turned off XOAUTH. Only XOAUTH2 is now supported. Detailt: https://developers.google.com/gmail/xoauth_migration

kerem 2026-02-26 01:30:40 +03:00

• closed this issue
• added the
  v1.5.9
  v1.5.8
  labels

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (May 7, 2015):

Thanks for the info. I'll try to get an update out soon.

<!-- gh-comment-id:99890326 --> @jberkel commented on GitHub (May 7, 2015): Thanks for the info. I'll try to get an update out soon.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@opello commented on GitHub (May 7, 2015):

I ran in to this yesterday and "disconnecting" (and then removing the authorization) and "reconnecting" to my GMail account seemed to fix things. I saved a debug log before and after and saw the change from XOAUTH to XOAUTH2. This was all using version 1.5.8.

<!-- gh-comment-id:99924537 --> @opello commented on GitHub (May 7, 2015): I ran in to this yesterday and "disconnecting" (and then removing the authorization) and "reconnecting" to my GMail account seemed to fix things. I saved a debug log before and after and saw the change from XOAUTH to XOAUTH2. This was all using version 1.5.8.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@mtomana commented on GitHub (May 7, 2015):

Yep, I have to confirm that it works, just like opello said :) But how is it possible? Is this just a workaround?

<!-- gh-comment-id:99927314 --> @mtomana commented on GitHub (May 7, 2015): Yep, I have to confirm that it works, just like opello said :) But how is it possible? Is this just a workaround?

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@opello commented on GitHub (May 7, 2015):

It seems like this is the announcement that says May 5 was the end of support for XOAUTH. The next time this might come up seems to be if/when XOAUTH2 goes away in favor of something more standardized.

Here is a log comparison of the two attempts.

<!-- gh-comment-id:99932307 --> @opello commented on GitHub (May 7, 2015): It seems like [this is the announcement](https://developers.google.com/gmail/oauth_protocol) that says May 5 was the end of support for XOAUTH. The next time this might come up seems to be [if/when XOAUTH2 goes away in favor of something more standardized](http://stackoverflow.com/a/24514691/131129). [Here is a log comparison](https://dl.dropboxusercontent.com/u/7256610/xoauth-to-xoauth2.html) of the two attempts.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (May 7, 2015):

I just checked the app, it actually does already support XOAuth2, however if you connect using the web flow it will still use XOAuth1. When authenticating using Android's AccountManager XOAuth2 is used. @opello maybe you still had an old token stored.

<!-- gh-comment-id:99955327 --> @jberkel commented on GitHub (May 7, 2015): I just checked the app, it actually does already support XOAuth2, however if you connect using the web flow it will still use XOAuth1. When authenticating using Android's AccountManager XOAuth2 is used. @opello maybe you still had an old token stored.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@opello commented on GitHub (May 7, 2015):

@jberkel Very likely, I'm going on a few years with this phone and install. @mtomana probably was in the same situation. I only checked for issues after resolving it and wondering if it was reasonable to think I should have been prompted to upgrade tokens. :)

<!-- gh-comment-id:99961993 --> @opello commented on GitHub (May 7, 2015): @jberkel Very likely, I'm going on a few years with this phone and install. @mtomana probably was in the same situation. I only checked for issues after resolving it and wondering if it was reasonable to think I should have been prompted to upgrade tokens. :)

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (May 7, 2015):

ok, so there will only be a problem for people who have an old token stored and for some reason can't use the android account manager. then there's also a big group of people who don't check the app (because it's running in the background) so it might make sense to release an update which automatically migrates old tokens.

<!-- gh-comment-id:99962627 --> @jberkel commented on GitHub (May 7, 2015): ok, so there will only be a problem for people who have an old token stored and for some reason can't use the android account manager. then there's also a big group of people who don't check the app (because it's running in the background) so it might make sense to release an update which automatically migrates old tokens.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@phireman481 commented on GitHub (May 8, 2015):

I'm completely illiterate when it comes to these things...that is why I donate to the developers. You guys do amazing work. Is there a timeframe for the update to fix the problem? I hate not having this backup to my Gmail.

<!-- gh-comment-id:100053188 --> @phireman481 commented on GitHub (May 8, 2015): I'm completely illiterate when it comes to these things...that is why I donate to the developers. You guys do amazing work. Is there a timeframe for the update to fix the problem? I hate not having this backup to my Gmail.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (May 8, 2015):

@phireman481 does the disconnect / reconnect trick @opello mentioned not work for you?

<!-- gh-comment-id:100055109 --> @jberkel commented on GitHub (May 8, 2015): @phireman481 does the disconnect / reconnect trick @opello mentioned not work for you?

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@phireman481 commented on GitHub (May 8, 2015):

@jberkel I honestly have no idea how to do that

<!-- gh-comment-id:100058634 --> @phireman481 commented on GitHub (May 8, 2015): @jberkel I honestly have no idea how to do that

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@opello commented on GitHub (May 8, 2015):

@phireman481 Open SMS Backup+, uncheck "Connect," then follow these steps to revoke the auth token. Once that's all done go back to SMS Backup+ and check "Connect" again, basically follow these steps.

The major down side to this approach is items that were added between the last successful sync and the first new sync will be lost. At least that's my understanding -- because I believe if you back up everything again you will have duplicates. But I might be wrong on this point.

<!-- gh-comment-id:100086950 --> @opello commented on GitHub (May 8, 2015): @phireman481 Open SMS Backup+, uncheck "Connect," then follow [these steps](https://github.com/jberkel/sms-backup-plus#user-content-faq-revoke-access) to revoke the auth token. Once that's all done go back to SMS Backup+ and check "Connect" again, basically [follow these steps](https://github.com/jberkel/sms-backup-plus#user-content-first-steps). The major down side to this approach is items that were added between the last successful sync and the first new sync will be lost. At least that's my understanding -- because I believe if you back up everything again you will have duplicates. But I might be wrong on this point.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@phireman481 commented on GitHub (May 8, 2015):

@opello Got it. Works perfectly again. Thanks so much for all the help.

<!-- gh-comment-id:100217139 --> @phireman481 commented on GitHub (May 8, 2015): @opello Got it. Works perfectly again. Thanks so much for all the help.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@ealprr commented on GitHub (May 10, 2015):

As mentioned, following @opello method will force a full sync of all events.
That should not be a problem for call and sms/mms log in Gmail because Gmail automatically delete duplicate messages (at least, in my case, I did not have duplicate logs).
However for calendar call log, it will duplicate events.

Here is a solution I used to clean my calendar:

1. Connect Google AppScript and create an empty project
2. Copy/paste the script [1].
3. In the first lines customize fromDate, toDate and calendarName. Ensure that delete_duplicate is set to false.
4. Save and choose a name for the project (for instance: Google Calendar tool).
5. Choose processCalendar function and run it ; allow Calendar access if asked.
6. Check output in View > Logs (ctrl+return) to validate parameters choosed in step 3.
7. If parameters are correct, set delete_duplicate to true and re-run processCalendar

[1]: Google AppScript:

// Set the calendar's name and the date range with duplicate event
var fromDate = new Date(2015,2,4,0,0,0); // March, 4 2015
var toDate = new Date(2015,4,7,0,0,0); // May, 7 2015
var calendarName = 'Call Log';

var delete_duplicate = false; // before deleting events, please check if parameters are correct

/**
 * Check 'calendarName's events between 'fromDate' and 'endDate' and report total number of events and number of duplicate events
 */
function processCalendar() {  
  var calendar = CalendarApp.getCalendarsByName(calendarName)[0];
  var events = calendar.getEvents(fromDate, toDate);

  var i = 0;
  var nb_duplicate = 0;

  while (i < events.length - 1) {
    var ev1 = events[i];
    var ev2 = events[i+1];

    // Log firsts and latest events to check 'calendarName', 'fromeDate' and 'toDate' parameters
    if (i < 6 || i > events.length-7) Logger.log('"'+ev1.getTitle()+'" ['+ev1.getStartTime()+' -> '+ev1.getEndTime()+']');

    // Check if the two events are equals (based on title, start and end time)
    if (ev1.getTitle() == ev2.getTitle() && 
      ev1.getStartTime().toString() == ev2.getStartTime().toString() && 
      ev1.getEndTime().toString() == ev2.getEndTime().toString())
    {
      nb_duplicate++;
      i += 2;

      if (!delete_duplicate) {continue;}
      // Delete the most recently added event
      if (ev1.getDateCreated() < ev2.getDateCreated()) ev2.deleteEvent();
      else ev1.deleteEvent();
    }
    else
      i++;
  }
  Logger.log("# total nb of event: " + events.length);
  Logger.log("# nb of duplicate event: " + nb_duplicate);
};

<!-- gh-comment-id:100630494 --> @ealprr commented on GitHub (May 10, 2015): As mentioned, following @opello method will force a full sync of all events. That should not be a problem for call and sms/mms log in Gmail because Gmail automatically delete duplicate messages (at least, in my case, I did not have duplicate logs). However for calendar call log, it will duplicate events. Here is a solution I used to clean my calendar: 1. Connect [Google AppScript](https://script.google.com/) and create an empty project 2. Copy/paste the script [1]. 3. In the first lines customize `fromDate`, `toDate` and `calendarName`. **Ensure that `delete_duplicate` is set to false**. 4. Save and choose a name for the project (for instance: `Google Calendar tool`). 5. Choose `processCalendar` function and run it ; allow Calendar access if asked. 6. Check output in `View > Logs` (ctrl+return) to validate parameters choosed in step 3. 7. If parameters are correct, set `delete_duplicate` to true and re-run `processCalendar` [1]: Google AppScript: ``` javascript // Set the calendar's name and the date range with duplicate event var fromDate = new Date(2015,2,4,0,0,0); // March, 4 2015 var toDate = new Date(2015,4,7,0,0,0); // May, 7 2015 var calendarName = 'Call Log'; var delete_duplicate = false; // before deleting events, please check if parameters are correct /** * Check 'calendarName's events between 'fromDate' and 'endDate' and report total number of events and number of duplicate events */ function processCalendar() { var calendar = CalendarApp.getCalendarsByName(calendarName)[0]; var events = calendar.getEvents(fromDate, toDate); var i = 0; var nb_duplicate = 0; while (i < events.length - 1) { var ev1 = events[i]; var ev2 = events[i+1]; // Log firsts and latest events to check 'calendarName', 'fromeDate' and 'toDate' parameters if (i < 6 || i > events.length-7) Logger.log('"'+ev1.getTitle()+'" ['+ev1.getStartTime()+' -> '+ev1.getEndTime()+']'); // Check if the two events are equals (based on title, start and end time) if (ev1.getTitle() == ev2.getTitle() && ev1.getStartTime().toString() == ev2.getStartTime().toString() && ev1.getEndTime().toString() == ev2.getEndTime().toString()) { nb_duplicate++; i += 2; if (!delete_duplicate) {continue;} // Delete the most recently added event if (ev1.getDateCreated() < ev2.getDateCreated()) ev2.deleteEvent(); else ev1.deleteEvent(); } else i++; } Logger.log("# total nb of event: " + events.length); Logger.log("# nb of duplicate event: " + nb_duplicate); }; ```

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@haridsv commented on GitHub (May 10, 2015):

@ealprr are you sure that we will not end up with duplicates if we choose to backup sms and call log again? I had this broken for the last 3 days so I don't want to choose skip unless the other option causes duplicates. I am guessing that the dedupe (if at all it is working) would be done by SMS Backup + itself and not by gmail.

<!-- gh-comment-id:100675640 --> @haridsv commented on GitHub (May 10, 2015): @ealprr are you sure that we will not end up with duplicates if we choose to backup sms and call log again? I had this broken for the last 3 days so I don't want to choose skip unless the other option causes duplicates. I am guessing that the dedupe (if at all it is working) would be done by SMS Backup + itself and not by gmail.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@ealprr commented on GitHub (May 10, 2015):

I am sure that Gmail delete duplicate messages.
Otherwise you would end up with duplicate messages when you send an email to a mailing-list which you suscribed (or any other way of receiving the same message several times.)
There is also the way Gmail expose labels though smtp which is folder: to apply labels to an email you need to copy/move the message in the desired folders. Hopefully, you do not duplicate the message for each label.
Finally, I recently did a full sync with SMS Backup+ with about 6k messages already synchronized and did not find duplicate.

However, you need to ensure to use the same Email address style in settings.

<!-- gh-comment-id:100682554 --> @ealprr commented on GitHub (May 10, 2015): I am sure that Gmail delete duplicate messages. Otherwise you would end up with duplicate messages when you send an email to a mailing-list which you suscribed (or any other way of receiving the same message several times.) There is also the way Gmail expose labels though smtp which is folder: to apply labels to an email you need to copy/move the message in the desired folders. Hopefully, you do not duplicate the message for each label. Finally, I recently did a full sync with _SMS Backup+_ with about 6k messages already synchronized and did not find duplicate. However, you need to ensure to use the same `Email address style` in settings.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@haridsv commented on GitHub (May 11, 2015):

Thanks @ealprr, appreciate your clarification.

<!-- gh-comment-id:100765824 --> @haridsv commented on GitHub (May 11, 2015): Thanks @ealprr, appreciate your clarification.

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@ctash commented on GitHub (May 14, 2015):

Thanks @opello! Those steps worked, I did have to do a full backup, as noted by @ealprr, but since I just unchecked and rechecked "connect", all my settings should be the same (which hopefully means no duplicates).

<!-- gh-comment-id:102058043 --> @ctash commented on GitHub (May 14, 2015): Thanks @opello! Those steps worked, I did have to do a full backup, as noted by @ealprr, but since I just unchecked and rechecked "connect", all my settings should be the same (which hopefully means no duplicates).

kerem commented 2026-02-26 01:30:40 +03:00

Author

Owner

Copy link

@kflaming1 commented on GitHub (May 15, 2015):

I have SMS Backup+ running in the background so I had hundreds of messages that weren't backed up by the time I noticed "Server does not support XOAUTH".

Here's what I've done:
I turned on access for less secure apps in Google Mail.
I turned on plain text authorization in SMS Backup+.
I filled in my email address and password .
I started a manual backup In SMS Backup+.
SMS Backup+ successfully logged in and backed up several hundred new messages including the call log.
I re-enabled XOAuth authorization in SMS Backup+.
I turned off access for less secure apps in Google Mail.
I disconnected and reconnected my Gmail account in SMS Backup+.
I skipped the initial backup because everything was now current.

I chose this approach to back up the items that were added between the last successful sync and the first new sync while avoiding the chance of any duplication.

I'm just hoping the disconnect/reconnect cleared out any old auth tokens because I'm not exactly sure on the procedure for doing that if it doesn't happen automatically.

<!-- gh-comment-id:102297069 --> @kflaming1 commented on GitHub (May 15, 2015): I have SMS Backup+ running in the background so I had hundreds of messages that weren't backed up by the time I noticed "Server does not support XOAUTH". Here's what I've done: I turned on access for less secure apps in Google Mail. I turned on plain text authorization in SMS Backup+. I filled in my email address and password . I started a manual backup In SMS Backup+. SMS Backup+ successfully logged in and backed up several hundred new messages including the call log. I re-enabled XOAuth authorization in SMS Backup+. I turned off access for less secure apps in Google Mail. I disconnected and reconnected my Gmail account in SMS Backup+. I skipped the initial backup because everything was now current. I chose this approach to back up the items that were added between the last successful sync and the first new sync while avoiding the chance of any duplication. I'm just hoping the disconnect/reconnect cleared out any old auth tokens because I'm not exactly sure on the procedure for doing that if it doesn't happen automatically.

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@jseideman commented on GitHub (May 18, 2015):

hi there--

amazing app. one of my favorites, and the one i send everyone to when they get a new phone.

now...this pesky XOAuth thing. my phone is older (DROID X running android 2.3.4) and therefore i cannot use the android account manager (unless i can??). I updated to 1.5.8 today (because of the android 2.x compatibility fixes) but i am still getting the XOAuth authorization error (and yes, IMAP is enabled in my gmail). Will there be a release that will also migrate the auth tokens? I would rather not have to disconnect from my account and lose my sync history if possible, and as I have an older phone, wont i still have to go through the web interface to authorize?

thanks!

<!-- gh-comment-id:102925094 --> @jseideman commented on GitHub (May 18, 2015): hi there-- amazing app. one of my favorites, and the one i send everyone to when they get a new phone. now...this pesky XOAuth thing. my phone is older (DROID X running android 2.3.4) and therefore i cannot use the android account manager (unless i can??). I updated to 1.5.8 today (because of the android 2.x compatibility fixes) but i am still getting the XOAuth authorization error (and yes, IMAP is enabled in my gmail). Will there be a release that will also migrate the auth tokens? I would rather not have to disconnect from my account and lose my sync history if possible, and as I have an older phone, wont i still have to go through the web interface to authorize? thanks!

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (May 18, 2015):

@jseideman yes it will happen, don't want to promise any exact dates though!

<!-- gh-comment-id:103131593 --> @jberkel commented on GitHub (May 18, 2015): @jseideman yes it will happen, don't want to promise any exact dates though!

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@jseideman commented on GitHub (May 18, 2015):

That's great! I know you said earlier in his thread that it may happen...I
was curious if it had made the leap from 'maybe' to 'yes it will happen'

Thanks!
On May 18, 2015 1:04 PM, "Jan Berkel" notifications@github.com wrote:

@jseideman https://github.com/jseideman yes it will happen, don't want
to promise any exact dates though!

—
Reply to this email directly or view it on GitHub
https://github.com/jberkel/sms-backup-plus/issues/554#issuecomment-103131593
.

<!-- gh-comment-id:103175579 --> @jseideman commented on GitHub (May 18, 2015): That's great! I know you said earlier in his thread that it may happen...I was curious if it had made the leap from 'maybe' to 'yes it will happen' Thanks! On May 18, 2015 1:04 PM, "Jan Berkel" notifications@github.com wrote: > @jseideman https://github.com/jseideman yes it will happen, don't want > to promise any exact dates though! > > — > Reply to this email directly or view it on GitHub > https://github.com/jberkel/sms-backup-plus/issues/554#issuecomment-103131593 > .

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@haridsv commented on GitHub (May 22, 2015):

Right now, the only two options are to skip all or backup everything. With thousands of SMS on my phone, I dread having to backup all (even though it doesn't seem to cause any duplicates), so I am experimenting with adding a setting to specify a date from which to backup the messages. I noticed that in the code, it uses -1 as the lower bound for the epoch timestamp initially, so I modified it to use a user specified preference. It seems to work nicely, except for a small issue with saving the preference (you may have to have to try multiple times to save the preference). Would anybody like to try it out and send me feedback? You can build it from my fork here:

https://github.com/haridsv/sms-backup-plus

For your convenience, I also created a binary release:

https://github.com/haridsv/sms-backup-plus/releases/tag/1.5.9-BETA4-HARI

I still have to figure out how to create resources for this preference, but it is hardcoded to show in English. The preference is at "Advanced Settings > Backup Settings > Backup Since Date".

<!-- gh-comment-id:104699355 --> @haridsv commented on GitHub (May 22, 2015): Right now, the only two options are to skip all or backup everything. With thousands of SMS on my phone, I dread having to backup all (even though it doesn't seem to cause any duplicates), so I am experimenting with adding a setting to specify a date from which to backup the messages. I noticed that in the code, it uses `-1` as the lower bound for the epoch timestamp initially, so I modified it to use a user specified preference. It seems to work nicely, except for a small issue with saving the preference (you may have to have to try multiple times to save the preference). Would anybody like to try it out and send me feedback? You can build it from my fork here: https://github.com/haridsv/sms-backup-plus For your convenience, I also created a binary release: https://github.com/haridsv/sms-backup-plus/releases/tag/1.5.9-BETA4-HARI I still have to figure out how to create resources for this preference, but it is hardcoded to show in English. The preference is at "Advanced Settings > Backup Settings > Backup Since Date".

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@opello commented on GitHub (May 22, 2015):

@haridsv I had considered this approach as well, wondering if I could use adb and sqlite3 (or something else) to manually reset the "last sync" date. I didn't pursue it as far as you because I only looking at losing 2 phone calls.

What I actually ended up doing was deleting all of my SMS and MMS messages and allowing sms-backup-plus to restore them. This took quite a while, but resulted in no lost data as far as I can tell.

Maybe some instructions for changing this wherever it persists would be a good manual solution for those facing this problem?

<!-- gh-comment-id:104717857 --> @opello commented on GitHub (May 22, 2015): @haridsv I had considered this approach as well, wondering if I could use adb and sqlite3 (or something else) to manually reset the "last sync" date. I didn't pursue it as far as you because I only looking at losing 2 phone calls. What I actually ended up doing was deleting all of my SMS and MMS messages and allowing sms-backup-plus to restore them. This took quite a while, but resulted in no lost data as far as I can tell. Maybe some instructions for changing this wherever it persists would be a good manual solution for those facing this problem?

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@haridsv commented on GitHub (May 23, 2015):

@opello I am a little paranoid in that sense. I lost about 5 days of sms and call log as I chose to skip all, probably not a big deal, but I wanted to get my hands dirty and I had a bit of time too. If I can get some feedback, then I could try to create a PR.

<!-- gh-comment-id:104879212 --> @haridsv commented on GitHub (May 23, 2015): @opello I am a little paranoid in that sense. I lost about 5 days of sms and call log as I chose to skip all, probably not a big deal, but I wanted to get my hands dirty and I had a bit of time too. If I can get some feedback, then I could try to create a PR.

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@Smsbackup commented on GitHub (May 28, 2015):

in 5/5/2015 my apps error by "Server does not support XOAUTH". for replace, i switching to plain text authentication but apps can't backup automatically, it just succeed in manual: fill all blank such as imap address,user nam/password anh click backup each time i login my apps. Who know why? help me, i want it auto.

<!-- gh-comment-id:106165453 --> @Smsbackup commented on GitHub (May 28, 2015): in 5/5/2015 my apps error by "Server does not support XOAUTH". for replace, i switching to plain text authentication but apps can't backup automatically, it just succeed in manual: fill all blank such as imap address,user nam/password anh click backup each time i login my apps. Who know why? help me, i want it auto.

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@opello commented on GitHub (May 28, 2015):

@Smsbackup If you have a current backup, try the steps mentioned above.

<!-- gh-comment-id:106613644 --> @opello commented on GitHub (May 28, 2015): @Smsbackup If you have a current backup, try the steps [mentioned above](https://github.com/jberkel/sms-backup-plus/issues/554#issuecomment-100086950).

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@Smsbackup commented on GitHub (May 29, 2015):

disconnect / reconnect as opello mentioned not work for me. The URL of the consent screen includes the string /oauth1, google said "you must migrate to OAuth 2.0". So sad for me. Do Opello know some apps like sms backup+ who auto sent sms backup to mail as schedule.

<!-- gh-comment-id:106653457 --> @Smsbackup commented on GitHub (May 29, 2015): disconnect / reconnect as opello mentioned not work for me. The URL of the consent screen includes the string /oauth1, google said "you must migrate to OAuth 2.0". So sad for me. Do Opello know some apps like sms backup+ who auto sent sms backup to mail as schedule.

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@castanedaru commented on GitHub (Jun 4, 2015):

Is not work for me too, from 01.06.2015 is trouble. "google no longer supports OAuth 1.0, you must migrate to OAuth 2.0 "
Your made amazing app. Please, fix it. i hope, that it possible.

<!-- gh-comment-id:108723217 --> @castanedaru commented on GitHub (Jun 4, 2015): Is not work for me too, from 01.06.2015 is trouble. "google no longer supports OAuth 1.0, you must migrate to OAuth 2.0 " Your made amazing app. Please, fix it. i hope, that it possible.

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (Jun 4, 2015):

hello everybody, can you please try this release: https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.9-BETA4

there's support for automatically migrating tokens in it but not sure if this works, since i cannot test it (impossible to get old xoauth1 tokens). it should automatically happen, but you might need to trigger the backup twice.

<!-- gh-comment-id:109045173 --> @jberkel commented on GitHub (Jun 4, 2015): hello everybody, can you please try this release: https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.9-BETA4 there's support for automatically migrating tokens in it but not sure if this works, since i cannot test it (impossible to get old xoauth1 tokens). it should automatically happen, but you might need to trigger the backup twice.

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (Jun 6, 2015):

try https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.9-BETA5 instead

<!-- gh-comment-id:109571306 --> @jberkel commented on GitHub (Jun 6, 2015): try https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.9-BETA5 instead

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (Jun 12, 2015):

Nobody able to test this? I'd like to do a new release soon
@castanedaru @Smsbackup

<!-- gh-comment-id:111426915 --> @jberkel commented on GitHub (Jun 12, 2015): Nobody able to test this? I'd like to do a new release soon @castanedaru @Smsbackup

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@castanedaru commented on GitHub (Jun 12, 2015):

Thank you!
I use version 1.5.9 on Android 5.0.2. No any troubles more.

<!-- gh-comment-id:111471043 --> @castanedaru commented on GitHub (Jun 12, 2015): Thank you! I use version 1.5.9 on Android 5.0.2. No any troubles more.

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@jberkel commented on GitHub (Jun 12, 2015):

great, thanks for the feedback. closing.

<!-- gh-comment-id:111471942 --> @jberkel commented on GitHub (Jun 12, 2015): great, thanks for the feedback. closing.

kerem commented 2026-02-26 01:30:41 +03:00

Author

Owner

Copy link

@drHeimskirk commented on GitHub (Jun 27, 2015):

Sorry to add to a closed bug but just wanted to give you some more information.
The 1.5.9 update finally made it to Google play and I updated today.

I could still not do a backup.

The logcat shows the following...
06-27 19:31:19.552 757 1408 W SMSBackup+: invalid response from server: HTTP/1.1 400 Bad Request
06-27 19:31:19.552 757 1408 W SMSBackup+: did not get a refresh token

This is on Android 2.2.

Is there something else that I should try or should I attempt the steps mentioned above to get things back on track.

Thanks.

<!-- gh-comment-id:115999903 --> @drHeimskirk commented on GitHub (Jun 27, 2015): Sorry to add to a closed bug but just wanted to give you some more information. The 1.5.9 update finally made it to Google play and I updated today. I could still not do a backup. The logcat shows the following... 06-27 19:31:19.552 757 1408 W SMSBackup+: invalid response from server: HTTP/1.1 400 Bad Request 06-27 19:31:19.552 757 1408 W SMSBackup+: did not get a refresh token This is on Android 2.2. Is there something else that I should try or should I attempt the steps mentioned above to get things back on track. Thanks.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

cyber1000-docker

multisim

update-build-process

gh-pages

jcrben-patch-1

workmanager

jcrben-patch-2

old-sms-backup

1.6.0-BETA2

1.6.0-BETA1

1.5.11

1.5.11-BETA22

1.5.11-BETA21

1.5.11-BETA20

1.5.11-BETA19

1.5.11-BETA18

1.5.11-BETA17

1.5.11-BETA16

1.5.11-BETA15

1.5.11-BETA14

1.5.11-BETA13

1.5.11-BETA12

1.5.11-BETA11

1.5.11-BETA10

1.5.11-BETA9

1.5.11-BETA8

1.5.11-BETA7

1.5.11-BETA6

1.5.11-BETA5

1.5.11-BETA4

1.5.11-BETA3

1.5.11-BETA2

1.5.11-BETA1

1.5.10

1.5.10-BETA1

1.5.9

1.5.9-BETA6

1.5.9-BETA5

1.5.9-BETA4

1.5.9-BETA3

1.5.9-BETA2

1.5.9-BETA1

1.5.8

1.5.8-BETA2

1.5.8-BETA1

1.5.7

1.5.7-BETA2

1.5.7-BETA1

1.5.6-DEBUG

1.5.6

1.5.6-RC1

1.5.6-BETA11

1.5.6-BETA10

1.5.6-BETA9

1.5.6-BETA8

1.5.6-BETA7

1.5.6-BETA6

1.5.6-BETA5

1.5.6-BETA4

1.5.6-BETA3

1.5.6-BETA2

1.5.6-BETA1

1.5.5

1.5.5-BETA2

1.5.5-BETA1

1.5.4

1.5.4-BETA2

1.5.4-BETA1

1.5.3

1.5.2

1.5.1

1.5.0

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.1

1.3.2

1.3

1.2

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1

1.0.11

1.0.10

1.0.9

1.0.8

1.0.7

1.0.6

1.0.5

1.0.4

1.0.3

1.0.2

1.0.1

1.0

Labels

Clear 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

Mirrored from GitHub 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 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 $~

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/sms-backup-plus-jberkel#469

No description provided.