Closed tinsaeDev closed 2 years ago
This is a new feature, I have added a new feature to support testing environment.
change testing
(ambiguous) to testEnvironment
. Also remove the yarn.lock
we generally ignore the package lock files for now.
I've updated the source per the feedback.
I have pushed some fixes, could you pull my changes on your master and run npm run doc
, then commit, push those changes. It should only add a single change that is options.testEnvironment
to the docs.
Hello
I hope this message finds you well. I apologize for reaching out to you directly, but I’m encountering an issue with logging in using a test number while attempting to submit my unofficial Telegram app version to the Play Store.
While I am able to log in using my personal number to the test environment, I’m having trouble with test numbers such as “+19996601234” (it works on iOS but not on Android). Please see the attached screenshot of my login attempt.
In the BuildVars file, I have set both DEBUG_VERSION and DEBUG_PRIVATE_VERSION to “true”.
Thank you for your help and assistance with this issue. I truly appreciate it.
Best regards,
npm run doc
Description
References