You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was my first time using this amazing tool (Big Fan!!!)
But encountered an issue while trying to log into WeChat using QR code authentication. Instead of logging in directly after scanning the code, the app asks for a verification code to be entered on the new device.
Steps to Reproduce:
Open WeChat on iOS 18.1.
Navigate to the QR code login screen.
Scan the QR code using WeChat on iOS 18.1.
Instead of logging in immediately, the app prompts for a verification code to be entered on the new device.
Expected Behavior:
After scanning the QR code, the login should be successful without requiring a verification code.
Actual Behavior:
A prompt appears asking for a numerical security code to be entered on the new device.
Environment:
Operating System: iOS 18.1 and macOS 15.2
Deployment Method: Docker
Additional Information:
Attached is a screenshot of the issue for reference.
The text was updated successfully, but these errors were encountered:
Hi,
It was my first time using this amazing tool (Big Fan!!!)
But encountered an issue while trying to log into WeChat using QR code authentication. Instead of logging in directly after scanning the code, the app asks for a verification code to be entered on the new device.
Steps to Reproduce:
Open WeChat on iOS 18.1.
Navigate to the QR code login screen.
Scan the QR code using WeChat on iOS 18.1.
Instead of logging in immediately, the app prompts for a verification code to be entered on the new device.
Expected Behavior:
After scanning the QR code, the login should be successful without requiring a verification code.
Actual Behavior:
A prompt appears asking for a numerical security code to be entered on the new device.
Environment:
Operating System: iOS 18.1 and macOS 15.2
Deployment Method: Docker
Additional Information:
Attached is a screenshot of the issue for reference.
The text was updated successfully, but these errors were encountered: