starred/sms-backup-plus-jberkel

Fork 0

mirror of https://github.com/jberkel/sms-backup-plus.git synced 2026-04-25 17:05:59 +03:00

[GH-ISSUE #1106] [BUG] This app is blocked #883

New issue

Closed

opened 2026-02-26 01:32:13 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 01:32:13 +03:00

Owner

Originally created by @paour on GitHub (Jan 31, 2024).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1106

Originally assigned to: @jberkel, @kurahaupo on GitHub.

Expected behaviour

When I trigger a backup, it should complete without error.

Actual behaviour

SMS Backup+ reports the following error: XOAuth authorization error. Please make sure you enabled IMAP in your Gmail account settings..

Play Services on my device displays a notification with the following alert:

Reproduce by

No response

Android version

11 (2020)

Phone brand

OnePlus

Phone model number

SMS Backup+ version

v1.6β

Messaging app

No response

Other details

No response

Originally created by @paour on GitHub (Jan 31, 2024). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1106 Originally assigned to: @jberkel, @kurahaupo on GitHub. ### Expected behaviour When I trigger a backup, it should complete without error. ### Actual behaviour SMS Backup+ reports the following error: `XOAuth authorization error. Please make sure you enabled IMAP in your Gmail account settings.`. Play Services on my device displays a notification with the following alert: ![Screenshot_20240131-141311](https://github.com/jberkel/sms-backup-plus/assets/90963/14701afa-a2e8-4e9d-97e3-bbc0bd71f90e) ### Reproduce by _No response_ ### Android version 11 (2020) ### Phone brand OnePlus ### Phone model number 8T ### SMS Backup+ version v1.6β ### Messaging app _No response_ ### Other details _No response_

kerem

2026-02-26 01:32:13 +03:00

closed this issue
added the
duplicate

xoauth
labels

kerem commented

2026-02-26 01:32:13 +03:00

Author

Owner

@paour commented on GitHub (Jan 31, 2024):

This looks like the end of the road. Even side-loaded, the app is blocked server-side by Google…

@paour commented on GitHub (Jan 31, 2024): This looks like the end of the road. Even side-loaded, the app is blocked server-side by Google…

kerem commented

2026-02-26 01:32:13 +03:00

Author

Owner

@pataquets commented on GitHub (Feb 11, 2024):

@paour #1102 stopped working?

@pataquets commented on GitHub (Feb 11, 2024): @paour #1102 stopped working?

kerem commented

2026-02-26 01:32:13 +03:00

Author

Owner

@paour commented on GitHub (Feb 11, 2024):

@paour #1102 stopped working?

Yes. I've been using app passwords forever because 2FA. I generated a new one when this cropped up, to no avail.

@paour commented on GitHub (Feb 11, 2024): > @paour #1102 stopped working? Yes. I've been using app passwords forever because 2FA. I generated a new one when this cropped up, to no avail.

kerem commented

2026-02-26 01:32:13 +03:00

Author

Owner

@marclaporte commented on GitHub (Feb 11, 2024):

Workaround: use a standard IMAP account (strong password always): https://github.com/jberkel/sms-backup-plus#usage-without-gmail-imap

@marclaporte commented on GitHub (Feb 11, 2024): Workaround: use a standard IMAP account (strong password always): https://github.com/jberkel/sms-backup-plus#usage-without-gmail-imap

kerem commented

2026-02-26 01:32:13 +03:00

Author

Owner

@kurahaupo commented on GitHub (Feb 13, 2024):

"This app is blocked" occurs when an app uses a Google API.

The reason that using IMAP works is that although it's provided by Google, it's not defined by Google.

The IMAP protocol does not transmit any identification of the app, so the server cannot know which app is using the IMAP connection, and can't use that to decide to block it.

So the question is, which Google API is being refused?

(My money would be on the contacts list API; I would test that by changing the default message format to include just the phone number and exclude the person's name.)

@kurahaupo commented on GitHub (Feb 13, 2024): "This app is blocked" occurs when an app uses a Google API. The reason that using IMAP works is that although it's _provided_ by Google, it's not _defined_ by Google. The IMAP protocol does not transmit any identification of the app, so the server cannot know which app is using the IMAP connection, and can't use that to decide to block it. So the question is, which Google API _is_ being refused? (My money would be on the contacts list API; I would test that by changing the default message format to include just the phone number and exclude the person's name.)

kerem commented

2026-02-26 01:32:13 +03:00

Author

Owner

@BenJewell commented on GitHub (Feb 23, 2024):

Still works fine for me using IMAP. Was getting a lot of errors a couple weeks ago but seems to have resolved itself.

@BenJewell commented on GitHub (Feb 23, 2024): Still works fine for me using IMAP. Was getting a lot of errors a couple weeks ago but seems to have resolved itself.

kerem commented

2026-02-26 01:32:13 +03:00

Author

Owner

@kurahaupo commented on GitHub (Apr 15, 2024):

Appears to be a duplicate of #1046

@kurahaupo commented on GitHub (Apr 15, 2024): Appears to be a duplicate of #1046

kerem referenced this issue

2026-02-26 01:32:37 +03:00

[PR #883] [MERGED] Updated Polish Play Store listing #1005