-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG : Play store rejected #180
Comments
Hey @nithiniz, Thank you for raising this issue. We are looking into it and will get back to you with an update. |
We have identified the issue and a solution is already defined for your issue, however, we would need some more information. Could you please share your email address if possible? |
Hey @nithiniz, |
@1abhishekpandey please get in touch at [email protected] Sorry, had some health issues and was hospitalized, so the delay |
Hello @nithiniz! Thank you again. |
Hey @nithiniz, |
Hi Abhishek/Chryssa,
Once again sorry for the late reply, I am being stretched at my current
project and was trying to get some slots. Seeing the current progress, I
will be available for this by early next week.
Thanks,
Nithin
…On Thu, Oct 24, 2024 at 10:06 AM Abhishek Pandey ***@***.***> wrote:
Hey @nithiniz <https://github.com/nithiniz>,
Just a reminder, we’ve sent you an email with the next steps and are
awaiting your response.
—
Reply to this email directly, view it on GitHub
<#180 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABHLWITDKXLETLR5YTMER3Z5B2M3AVCNFSM6AAAAABOWAPQG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZUGI3TINJXGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Describe the bug
Please provide the following information:
1 While submitting build to playstore with the sdk version 1.2.0, we are getting a rejection message
Which platform is the issue occurring on
Is the error occurring on:
Expected behavior
App Approved in Playstore
To Reproduce
Steps to reproduce the behaviour:
*Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: