mirror of
https://github.com/PlayCover/PlayCover.git
synced 2026-04-26 00:05:52 +03:00
[GH-ISSUE #950] (TikTok) Question: This thing, last time I ran it, did this with no question asked (along with a bunch of other stuff) #476
Labels
No labels
UI
app-support
bug
bug
documentation
duplicate
enhancement
game-support
good first issue
help wanted / caution
inactive
invalid
macos-beta
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PlayCover#476
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 @KirinVittel on GitHub (May 11, 2023).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/950
Why does it do this? Is it Tiktok being malicious or the people cracking it or just happens to be a side effect of how the app is built?
This thing, last time I ran it, did this with no question asked (along with a bunch of other stuff)

(That's the least of its problems, btw. Just use the web version if you don't want your Home folder to potentially be absolutely nuked)
Originally posted by @ohaiibuzzle in https://github.com/PlayCover/PlayCover/discussions/628#discussioncomment-4498200
@ohaiibuzzle commented on GitHub (May 11, 2023):
Fun fact: on normal iOS devices, this file is protected and apps can't access it. (Obviously you don't just get to read the user's call history)
So this is more than likely TikTok's own behavior upon detecting a jailbroken device (which PlayCover technically is) to read these files for its own usage
@KirinVittel commented on GitHub (May 11, 2023):
Interesting thanks, do you have any idea if it affects the iPhone jailbreaker? Don't see it talked about
@ohaiibuzzle commented on GitHub (May 11, 2023):
I mean jailbreaking does also smash the app sandbox so... Technically?
Although again they could, like the clipboard access fiasco, say that it's debugging or SDK-related stuff. Hard to tell
The only way we can know for sure is to debug the app on iOS to see what it does there