I logged in ~1500 people via Account Kit (basic web) in the last 12 hours.
However, in Facebook Analytics, the Account Kit funnel shows 2.65% conversion, with 754 people at the starting point, and 20 people at the end.
Whichever way I slice or dice it, this is inaccurate reporting.
This Account Kit funnel was auto-generated for me. I don't seem to have control over editing it in Facebook-Analytics. For starters, I can't even tell whether this reporting error emanates from Account Kit, or from Facebook Analytics.
Can you help?
Hey I just wanted to check with you and see if you're still having this issue?
Things should be working fine from the AccountKit side now, but if you're still having an issue please submit a request with your app id on: https://developers.facebook.com/bugs/
Related
We have received a notice from Google Play that our app will be removed if we do not provide them with login credentials in our app. The problem is that our app is a second-screen game, where the primary screen is a desktop game which provides a four digit code for people to enter in our app and log on to the game. Our app has been in the Play Store for years and is quite popular.
Google Play has given us until Oct 4th to provide them with a code, otherwise our app "may be removed from the Play Store". We have set up a desktop computer running games in loop 24-7 until they have reviewed our app, and we have provided them with a link to a twitch stream where the game runs in loop.
It's now been seven days and we have not heard anything from Google Play. It's very frustrating that there is no personal contact, we only receive auto-generated bot/AI mails about policy violation.
Does anyone know what further action we can take to make sure our app is not removed? We have "contacted support", although contacting support in Google Play means just writing your app name and email address in a form and selecting a radio button of what the problem seems to be (none of them apply exactly). No response for days.
This is the original warning mail from Google Play:
Hi Developers at xxx, After a recent review, we’ve identified that we
need additional information about your app xxx in accordance with our
policies. Please resolve the issue described below by October 04, 2022
to avoid further action against your app. Reasons of violation Issue:
Need login credentials for app review In order for us to review your
app for compliance with Developer Program Policies, we will need you
to provide valid login credentials for your app. If users need
credentials to access your app, please provide all appropriate
credentials via Play Console. If you previously supplied credentials,
please ensure that they have not expired. If your app normally uses
2-Step Verification (e.g. SMS verification), biometrics (e.g. a
fingerprint or face scan) or a location-dependent password (e.g.
geo-gate), please provide valid demo credentials that we can use
instead.
in Google Play Console in app content > app access > Add new instructions
in password field write down the 4-digit code.
in Any other instructions Write a detailed step-by-step guide on how to walk through game until the 4-digit code entered, and provide them with a valid digit code (that always works) and write that this is a "Demo Digit code".
Also, provide them with a video just to the point of entering the code and logging in (the shorter the video the better)
And you will have to wait, it takes a lot of time do not worry.
We've just published our first app in Google Workspace Marketplace (a google docs add-on) and can't figure out how, or if, it is possible to setup an email or other notification (slack notification would be cool) for our Customer Success team to be notified when a user leaves a review of the app.
Appreciate that if we get thousands we will probably turn the notifications off (or filter them in some way), at this early stage though, we're very eager to act on any feedback.
Thanks!
Disclaimer: I am creator of Obsei, and this might be biased answer.
You can try Obsei: an open-source low-code AI powered automation tool.
It can monitor App and Play stores for customer reviews and send notification Slack when someone add review there. Also Obsei can classify review contextually to classify it into issue categories. Refer below image.Obsei workflow
All of these can be achieved free without any cloud hosting requirement. Refer link for more detail.
Happy to answer any queries in this regards.
I built a Chrome Extension using the Google Slides API ~8 months ago, with users having to sign in with the OAuth consent screen as to be able to use the extension. The extension has over a thousand users, and for the past weeks I've had reports of people seeing an error that says "Sign in with Google temporarily disabled for this app".
I checked and indeed the OAuth page was still "being verified", although it still said it would only take a few days / several weeks. I'm not using any sensitive scopes either, so it all seems very odd. If the app didn't meet the criteria I would have been rejected, but that doesn't seem to be the case.
So my question is, how can I get it verified, or if anything rejected so that I can make a new submission? I looked all over the place and I haven't found a way to get it unstuck. I'm pretty sure 8 months for verification isn't normal whatsoever.
Google seems to manually validate each OAuth screen. That's a long (and costly process), but to my experience, it generally takes 24 hours if you don't use any sensitive/restrictive scopes. As it's your case apparently, I presume your submission has probably being lost somewhere.
My recommendations:
Check in the Google Cloud Console the status of your OAuth Screen. After logged in Google Cloud console, click on the hamburger icon and select "APIs & Services" > "OAuth consent screen". At the top of the page you will see the status. If it's something like "pending verification", go to step 2. Otherwise, make sure the form is completed and submit it to verification again.
Search in your emails if you have been contacted by "api-oauth-dev-verification-reply [at] google [dot] com" (the address might slightly change as they use a ticketing solution). Maybe they tried to contact you but the email went to spam?
Get in touch with the OAuth team by emailing "api-oauth-dev-verification-reply [at] google [dot] com". Make sure to add your
Google Project number in your email, so they will be able to check
what's wrong.
Disclaimer: I don't work at Google. But I'm bit familiar with that process now :)
I'm developing an application with react native and I am using this library
https://github.com/tipsi/tipsi-stripe in order to use Google Pay with stripe integration.
I already linked the test key from stripe and the merchant Id from play store.
I have a serious issue though. After running the app, when the Google Pay popup form opens,
i get the Google Pay dialog but with a message
"Unrecognized app. Please make sure you trust this app
before proceeding".
However when I enter a test card and press continue I get an additional error that says
Transaction declined: invalid payment method. [OR-CCSEH-05]
I would appreciate any help.
See image below
When testing Google Pay, you actually use real credit cards. That said, I'd be doubly positive you've got your environment set to use Test Mode in Google Pay. Outside of Tipsi, you'd usually set that with the WalletConstants.ENVIRONMENT_TEST constant. Hope that helps!
i've contacted google regarding this case, as i've been facing similar one and upon it's inspection i've received the following reply:
Thanks for being Patient. I apologize for the inconvenience caused.
Upon checking, I understand that you're unable to add testing cards. I would like to inform you that testing cards can't be added to Google Payment profile as payment Method.
Thanks!
upon further investigation by Stripe it self i've been assured:
For a bit of context on how Google Pay works to test payments. When you’re using your test mode API keys, the actual details of the card are ignored, and they get replaced with the Stripe 4242 test card. To test authentication you will not be able to add the test cards to your Google Pay account however there is a work around for this, you add our 3DS test cards to Chrome and use the PaymentRequest button with them (making sure to choose them, and not Google Pay itself). Unfortunately there is no direct method to testing this in your the app.
so setting WalletConstants.ENVIRONMENT_TEST at 5th step of their tutorial should be sufficient and then use your real card.
https://developers.google.com/pay/api/android/guides/tutorial
Recently, I have received a message from Google Play Developer saying that one app was removed:
This app has been removed from Google Play for a violation of the
Google Play Developer Program Policy regarding Ad Walls and
Interstitial Ads. For additional information, please review the
interstitial ads help article, then correct your app's ads and
resubmit. Additional details have been sent to your account owner's
email address.
So I've heard that if I get 3 strikes like this one, my account will be terminated. Is that true?
Also, I am only using Admob ads.
Google's policy here states that
Removals
Don’t impact the standing of your Google Play Developer account.
Once your app is removed, the published version of your app won’t be available on Google Play until a compliant updated is submitted.
The message you quoted says that your app was removed, so you don't have much to worry. You just have to be more careful about following the Ads guidelines. They don't want you to keep publishing many apps that don't follow the rules.
Also, they don't define exactly how many Suspensions you can have:
Suspensions
Count as strikes against the good standing of your Google Play Developer account.
Egregious or multiple policy violations can result in suspension, as can repeated app rejections or removals.
But 3, as you mentioned, seems a fair number in a short period. Remeber: your apps won't be suspended for nothing, so take care to follow correctly the instructions.
It says right there that "Additional details have been sent to your account owner's email address". So that would be the place to look to get the specifics.
There are a variety of reasons that your app may have been reported. For instance, you should probably let people know that there are ads at all. Is your app rated as "kid friendly" but the ads are not?
I'm going to guess that it has something to do with placement. For instance, if people are clicking your ad accidentally because it's too close to another actionable item, that will get you in trouble.
It could also be because someone is clicking the ad repeatedly, during testing, or to be a joker. And it's raising a flag.
You really need to do your own research to find out what the problem is.
Once you've done with that, correct the problem and try again.