In the area of "Let us know whether your app contains ads" in App Content, this section tells me that I have to complete the next section
You must let us know whether your app contains ads. The 'Contains ads' label is shown next to apps with ads on Google Play. Make sure this information is accurate, and is kept up to date.
here
But when I go to the option, it just show me
this
For me, it was the Ad Blocker. I disabled my adblocker and refreshed the page and it worked.
#Mate Farkas's answer (worked on phone) inspired me to test this.
Try to complete the section on your phone.
I'm chasing the same issue for an hour now. On Chrome+MacOS I'm seeing the same error as you, on Chrome+Android (Pixel 2) it works for me.
I ended up downloading Chrome to see if the problem was the browser (I was using Edge Chromium), and the option appear, seems like is a bug with Edge Chromium.
Related
I am using applovin ads in my android app, but the ads are too long and not able to click on the close as well.
The user experience is too bad. Also the ads are shown as tow cycles. It leads to the loss in user retention.
Kindly let me know any one facing the issue like the same.
I have followed this doc to show the interstitial ads in my app.
https://dash.applovin.com/documentation/mediation/android/getting-started/interstitials
Sorry for the late answer. May be you did it but if you don't someone also facing the same issue because I am also facing this issue. It is a bug in MaxAd in "testing Mode". You can check it while downloading from play store and on a real time device.
its easy to setting time in applovin, by going to discovery and Application go to video setting and adjust
enter image description here
hope thats answer your question
Screenshot:
You can see I am not able to do anything here, is this a bug or am I missing something to fill before coming to this page?
Other screenshots for reference:
I talked to google developer support, they told me to turn off adblock. I did that and refreshed and was able to see the content on the page successfully. Hope that's the same thing you're dealing with here.
I am building an Android app that signs in users to GitHub using OAuth. I followed the instructions here to do so. As the first part of the process, I sent users to the URL
https://github.com/login/oauth/authorize?scope=repo&client_id=MY_CLIENT_ID
However, when I sign in on my Android device, the Authorize xxxx button appears to be greyed out and I can't click it. Does anyone have a clue why this is? (Large screenshot below)
I think the button may not have been greyed out before, the first time I ran the app and signed in. However, I can't tell for sure because I was in a rush.
So, I pasted the link into Chrome on my computer and the OAuth process worked fine. I noticed the button was greyed out at first, but then became bright green. This got me wondering: was JavaScript enabled by default in the Android WebView? Sure enough, it wasn't. I found this answer which details how to enable JS. This was the key line that got everything working:
webView.getSettings().setJavaScriptEnabled(true);
I absolutely support what #james-ko said - JS has to be enabled for the WebView.
But sometimes it doesn't help. I found a little bit more info and would be happy to share it here.
Similar story - I have an app which is supposed to login the user with GitHub OAuth, everything works fine except the "Authorise" button - it just stays disabled whatever setting were applied is some cases.
Here is summary:
The button is always stays disabled on emulator with API 22 and 23 (I didn't try 24-27 though) regardless of settings and user behaviour.
It works well on emulator with API 28 and 29.
On the real device Pixel 3 (API 29), the button was disabled initially and nothing was happening for a while. But when I taped the screen twice in random places it got enabled. The app restarting reproduces the situation: initially disabled button --> tap on the screen --> button gets enabled.
Apparently some antifraud mechanism is involved.
But it gives kinda poor experience to the final user it looks like a bug in the app and there is not much what we can do about it :-/
I had the same problem in Safari, but I located a potential cause, the content security policy of the site was set to: script-src github.githubassets.com
Im making this question because, i dont know if im the only one who happened this and how to fixed. In the last month i been acceding to the android.developers site without having any problem, but in the last 2 weeks, it started to show posts in korean, like this:
and it happens in all the site, showing me parts in korean and parts in english. I tryed to access to manually to the site, but it still resending me to the "ko" extension. I have the computer in russian and i dont know if that influences the search. I didnt find anything related to this, and it starts to be really annoying. Thanks!
I had this happen to me too! Clear your cookies and cached app data in settings. Google chrome: Ctrl-H, clear history, check only the above options. Close browser, re-open and check if it is still the same. This happened to me when I clicked on a Korean link to google dev page last week.
At the bottom of the page you can simply choose the language you want and the menu will be in the right language again.
If it happens again: when you have the "intl/ko/" in URL -> just replace "ko" by "en".
IT works just right now (after months of research...)
Rather than clearing your complete browser data,
Right click -> Inspect Element -> Click on Resource Tab Now select
'Cookies' menu -> select developer.android.com Here delete
'android_developer_pref_lang'
Now close this Tab. Open develop.android.com in new tab.
In Chrome, from the javascript console (F12-Application-Console):
document.cookie = 'android_developer_pref_lang=en; path=/'
and then refresh the page
I feel a little bit silly asking this, but I haven't been able to find any answers on my own. My Force Close dialog has a "Report" button. I think it's a great idea, and I wish everyone had it. At first, I thought it must be something I turned on without realizing it, but not only can't I find any setting that I might have touched, I also can't find any reference to this button existing on the Internet. I have a Droid, and I know 4 other people with Droids, and they say they don't have the option to report Force Closes. Am I special? Am I just missing something? The "report" button has been there for at least a few weeks now.
When I use the Report button, I get a screen with a "feedback" field and a checkbox for "Include system data". Below that , it says "Information from feedback reports will be shown to the developer of the application." Under that are Preview and Send buttons.
As a developer, I've never received one of these reports.
I'd try to send a report to myself, but it seemingly only shows the button for apps installed from the market, and I don't know of a way to crash my production app.
I suppose I could publish a simple crashing app just to try it out, but I thought I'd ask you folks first.
Edit:
You can view screenshots here: http://bentobin.com/crashReportImages/
This is a new feature of Android :)