Many users are suddenly being asked by TikTok for their iPhone passcode for some unclear reasons when accessing the video-sharing app.
The weird occurrence was first noted by several Reddit users a month ago after the passcode display suddenly popped up when opening the app.
Users reported being asked to "enter iPhone passcode for 'TikTok'." The passcode request can be canceled and the app will proceed to the "For You Page" normally, baffling users even more.
TikTok Asking for iPhone Passcode?
byu/InspiringLizard inTiktokhelp
TikTok, like most social media apps on Android and iPhone, is supposed to launch without a passcode or ID verification requirement every time.
As of writing, there are still no clear reasons for the unsolicited passcode requests appearing on some iPhone devices.
TikTok iPhone Passcode Requirement: Likely Cause
While both companies have yet to give their explanations on the matter, the passcode requirements started occurring coincidentally after Apple released two urgent security updates for iOS devices.
The Dec. 11 security update is supposed to fix a bug that allows access to sensitive user data.
Experts told the New York Post that Apple's security update may have triggered TikTok's "restricted mode" when accessing user data from their devices.
No matter the cause for the glitch, experts strongly advise users to not provide their iPhone passcodes when encountering the sudden requirement notification to secure data privacy.
TikTok has already been caught in the past monitoring journalists writing about the company, obtaining their IP address and user data without permission.
Related Article : FTC Pushes for New Regulations to Protect Kid's Data Privacy
TikTok iPhone Passcode Requirement: Quick Fix and Workaround
The fastest way to remove the weird notification is to remove TikTok from the iPhone's "restricted mode."
This can be done by going to TikTok's settings and turning off the restriction under the "content preferences" section. However, it might not be needed anymore in most cases.
Many users reported that the error has disappeared along with the arrival of the version 32.5.0 of the app.
