[GH-ISSUE #26] Unable to locate google drive file map for: com.whatsapp #22

Closed
opened 2026-02-25 20:34:29 +03:00 by kerem · 5 comments
Owner

Originally created by @maamirh on GitHub (Sep 26, 2019).
Original GitHub issue: https://github.com/B16f00t/whapa/issues/26

I tried many solutions and follow every guide but i am getting this error "Unable to locate google drive file map for: com.whatsapp" every time .

Every thing was working fine before .I am getting this error from some days .I think google or whatsapp changed the policies .

Kindly handle this issue.

Originally created by @maamirh on GitHub (Sep 26, 2019). Original GitHub issue: https://github.com/B16f00t/whapa/issues/26 I tried many solutions and follow every guide but i am getting this error "Unable to locate google drive file map for: com.whatsapp" every time . Every thing was working fine before .I am getting this error from some days .I think google or whatsapp changed the policies . Kindly handle this issue.
kerem closed this issue 2026-02-25 20:34:29 +03:00
Author
Owner

@B16f00t commented on GitHub (Sep 26, 2019):

Ok in principle, the accounts I've tried work perfectly. I'm trying to get some account out of that error to analyze the requests. So so far we have to wait for it to fix the problem.

<!-- gh-comment-id:535623042 --> @B16f00t commented on GitHub (Sep 26, 2019): Ok in principle, the accounts I've tried work perfectly. I'm trying to get some account out of that error to analyze the requests. So so far we have to wait for it to fix the problem.
Author
Owner

@BriggBongo commented on GitHub (Sep 27, 2019):

Have you recently changed phone(but migrated WhatsApp number to the other new phone in the same Google drive account) since it broke with that message?

Also have you tried to initiate a new backup via the phone manually?

I am also trying to find a common denominator.

Only thing that's changed since it stopped working for me is i bought a new phone (galaxy s10 android pie with latest whatsapp as at sept 2019) and migrated my WhatsApp number to the new phone so upon installing WhatsApp it downloaded a cooy of my data via the same Google identity and has been backing up successfully since then. The other phone was decommissioned and factory reset. Nothing changed in the config and i get same error as you.

Further more i started with a fresh log file and folder for the backup repo but same error.

<!-- gh-comment-id:535755726 --> @BriggBongo commented on GitHub (Sep 27, 2019): Have you recently changed phone(but migrated WhatsApp number to the other new phone in the same Google drive account) since it broke with that message? Also have you tried to initiate a new backup via the phone manually? I am also trying to find a common denominator. Only thing that's changed since it stopped working for me is i bought a new phone (galaxy s10 android pie with latest whatsapp as at sept 2019) and migrated my WhatsApp number to the new phone so upon installing WhatsApp it downloaded a cooy of my data via the same Google identity and has been backing up successfully since then. The other phone was decommissioned and factory reset. Nothing changed in the config and i get same error as you. Further more i started with a fresh log file and folder for the backup repo but same error.
Author
Owner

@TehBotolSosro commented on GitHub (Sep 27, 2019):

if i tried the normal method it give me "Unable to locate google drive file map for: com.whatsapp"
but changing it to the alternate download method works fine without issue
so try the alternate download option

<!-- gh-comment-id:535852634 --> @TehBotolSosro commented on GitHub (Sep 27, 2019): if i tried the normal method it give me "Unable to locate google drive file map for: com.whatsapp" but changing it to the alternate download method works fine without issue so try the alternate download option
Author
Owner

@BriggBongo commented on GitHub (Sep 28, 2019):

Alternative version works in whatgodri. Issue was with spacing in the cfg file. Furthermore the original reason that the original method of sync didn't work was my backup files was corrupted and only new data from the new phone backup was there and not historical ones. Plus because of the messing around with this i started liking python and kind of developed an interest in it :)

<!-- gh-comment-id:536146895 --> @BriggBongo commented on GitHub (Sep 28, 2019): Alternative version works in whatgodri. Issue was with spacing in the cfg file. Furthermore the original reason that the original method of sync didn't work was my backup files was corrupted and only new data from the new phone backup was there and not historical ones. Plus because of the messing around with this i started liking python and kind of developed an interest in it :)
Author
Owner

@maamirh commented on GitHub (Oct 1, 2019):

Alternate method is working and resolved my issue.

<!-- gh-comment-id:536930614 --> @maamirh commented on GitHub (Oct 1, 2019): Alternate method is working and resolved my issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
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/whapa#22
No description provided.