search

Razviar / marvelsnaptracker

Marvel Snap Tracker repo
https://marvelsnap.pro/
162 stars 35 forks source link

Samsung Android App Issue #58

Open NavyVet81 opened 11 months ago

NavyVet81 commented 11 months ago

I'm having an issue with my Samsung not allowing access to the data folder to allow the tracker to see the logs. Other than copying the nvprod folder to another location everytime I play, is there a work around for Android/Mobile devices?

justfool commented 11 months ago

Same issue on my pixel 4a, cannot locate game data

Razviar commented 11 months ago

Hi! The first question would be - have you launched Snap at least once on your device before trying to sync the tracker? The second is - can you locate log folder manually on your phone, using regular file explorer?

justfool commented 11 months ago

Hi Raviar,

  1. Yes, I had played Snap several times before installing the tracker.
  2. I Guess no, the google files APP shows nothing in Android/data (Android 13 without root on pixel 4a).

Razviar @.***> 於 2023年10月25日 週三 下午2:15寫道：

Hi! The first question would be - have you launched Snap at least once on your device before trying to sync the tracker? The second is - can you locate log folder manually on your phone, using regular file explorer?

— Reply to this email directly, view it on GitHub https://github.com/Razviar/marvelsnaptracker/issues/58#issuecomment-1778583503, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWGOJBKOLXE52HPORDXGMLYBCVAPAVCNFSM6AAAAAA6OLMVRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZYGU4DGNJQGM . You are receiving this because you commented.Message ID: @.***>

tempbugreporter commented 11 months ago

Same issue on my pixel 6

invasionofsmallcubes commented 10 months ago

Same here, it seems the right permission to access the directory are missing. In my case it's under /Android/Obb

invasionofsmallcubes commented 10 months ago

Sorry I just wanted to add for me the behaviour appears on Oxygen 13. Device is a OnePlus Nord CE 2 Lite.

DerykHopley commented 9 months ago

So just to add to this conversation. I have this same issue with Android 13 (seems permissions have been changed) but I have a manual work around (not ideal by works).