I was doing tests with admob, I innocently linked an existing application in the playstore that is not mine, obviously I was not going to create it, I clicked on the close button but Admob linked the applications.
Obviously I do not have any ad unit, but I can not modify or delete the application to remove in link between that admob app and the playstore app.
Can Admob suspend my account for this error?
Can remove that link between the Admob app and the Playstore app?
You cannot delete an app from your AdMob account, although you can hide it as mentioned here
Admob doesn't have any direct policy about connecting someone else app to your account, so no one can tell you for sure but it's quite improbable that they will suspend your account. And I have this opinion on the base that in the "Adding A Link To Your App" documentation , they have only warned us like this(only):
Make sure you link the correct app. You can't change it later.
I have read somewhere that in earlier Admob version you could delete your app from App Settings page (and that version is still live, but not accessible from the Admob URL, you may search for it)
In the end, I'll say just hiding your app is enough.
Related
So this is my first Android app. I made a mistake and set up my Admob account as an individual when my App operates under my company. So, after doing the research it appears that once I establish an Admob account I can't change the type (from individual to entity).
So I have to close it and create a new account. But I was wondering if I need to remove all the Admob code from my app before I close the account? Or can I just leave it be and once the account is closed the Admob SDK will just ignore the request to serve an ad since the account would be null.
I don't want to close the account and the activity of Admob searching for an invalid account causing the app to crash. However, I don't want to roll out a whole new app version if I don't have to. I'll have to roll out a new version anyway once I square away a new Admob account.
My gut tells me Admob would just ignore it and not crash the app, but I don't want to assume since my level of expertise it not that high in this area. Any insight would be appreciated.
to my knowledge, if you have caught events in your code like not internet, or failed ads loading, then deleting your Admob account doesn't affect anything, it's just like you wrote the wrong id, your app still works normally
I got the following problem:
I published an app that had to do with Corona. I didn't know that Google doesn't allow this (unless it's approved by your government in some way), so Google disabled the app directly.
I have tried to just delete it then, so it doesn't appear in the Dashboard anymore, but I couldn't find how to do this. I've searched the internet on how to delete disabled apps and it seems like that is not possible.
Now that would be fine, but there's the following issue:
Since it was disabled, Google Admob says "one of my apps violates the terms of use of Admob". There also isn't a direct problem with that, but Admob just sent me an E-Mail yesterday that says
Google will introduce a new strike-based system to enforce against advertisers who repeatedly violate Google Ads policies
So I need to remove the App. How can I do that?!
Here's a screenshot that shows that everything is greyed out and therefore I cannot delete the app the normal way:
You can't do it unfortunately. The only thing you can do is fix the problem and only then delete it.
You can do it by select app and then setup option > Advance setting here you can unpublish and more setting with you app
The application worked fine for half a year, I tried to upload an update, everything was as usual, but the console received "We have determined your app contains code to facilitate Ad Fraud", although I almost did not change anything. The only change that had at least some relation to the advertisement, after the splash, an advertisement appears, after it is closed, it shows the main screen of the application, it was decided to extend the display time of the splash screen, so a slight delay was added so that the advertisement had a little more time to load. After that, the update failed.
We wrote in support, after almost 2 weeks, they replied:
"I’ve reviewed your appeal request and found that your app still violates Google Play Policy. I’ve included details below about the specific issue with your app and what you can do to get your app back on Google Play.
Step 1: Fix the policy violation with your app
During review, we found that your app violates the Ad fraud policy:
Your app is not compliant with the Ad Fraud policy. Ad fraud is strictly prohibited. Ad interactions generated for the purpose of tricking an ad network into believing traffic is from authentic user interest is ad fraud, which is a form of invalid traffic.
Ads should not be shown in a way that results in inadvertent clicks. Forcing a user to click an ad or submit personal information for advertising purposes before they can fully use an app is prohibited.
Ads should not appear after the user has exited the app, or after the user has pressed the back button to exit the app.
Ads associated with your app must not interfere with other apps, ads, or the operation of the device, including system or device buttons and ports.
This includes overlays, companion functionality, and widgetized ad units. Ads must only be displayed within the app serving them. You can refer the attached screenshot for additional information.
You can read through the Ad Fraud policy page for more details and examples of common violations.
Please update your app to fix this issue. You may also want to double check that your app complies with all other Developer Program Policies, as additional enforcement could occur if there are further policy violations.
Step 2: Submit an update to your app
To submit an updated app bundle or APK:
Prepare your updates.
Create a new release using the compliant app bundle or APK. Be sure to create the new release on the same track(s) as the non-compliant app bundle or APK, increment the version number, and set the release to 100% rollout.
Follow the on-screen instructions to add APKs or app bundles, then review and roll out your release.
Please let me know if you have any other questions. Thanks for working with us to fix the policy issue and for your continued support of Google Play."
It seems like the application does not break anything, but I came across this answer Uncaught exception thrown by finalizer: All WebView methods must be called on the same thread. (Expected Looper ) th / 57308639 # 57308639 it is possible if the application is minimized and the advertisement is loaded and is shown not in the application. Or, due to problems with the connection, it does not show ads immediately after the splash, but passes it to the main screen and then it already shows that it also seems to be wrong, but then problems with the update appeared earlier. Could any of this be a problem? What else could be the problem? Maybe someone did something similar, please tell me what are the solutions?
Update Admob library to 19.7.0 or later and follow the migration guide to update Rewarded and Interstitial Ads in the app.
I understand Admob is getting an overhaul, but I don't see why I can't sign up for an Admob account.
I am using my Gmail account, but when I go to https://apps.admob.com/admob/ a red bar at the top of the page shows up saying "An error has occurred. Refresh the page and try again".
I don't even have Adblock downloaded, as I know that helped some people. Also, my secondary Gmail account seems to be able to proceed on from the first step. I really think I should be using the same Gmail account that is also used for my Android developers account.
I have contacted support and they say simply open an incognito window (and I have done so), and I made sure some of the network certificates are cleared, and that my extensions were disabled.
Any insight would be appreciated. The account will be 18 in less than a month if that helps at all, and I also was about to go through the Adsense process (I don't think I actually sent my application).
An ad blocker can cause this as well. Disable ad blocker and try again.
In your adsense account go to access and authorization section and click on AdMob account and select current account as preferred account.
This may not have been the best place to ask this question but I have seen similar.
Basically, there have been some big revisions to the Admob service, so if you happened to have submitted an application with Adsense, your account may get the error I described above. The best advice I can give is just to contact the Help Center!
Now I managed to sign the apk (using Eclipse Android Tools) and adb install .. to the device for testing.
But this removed the debug function, e.g. "step over" which make problem tracing much more difficult.
Is it possible to debug the inapp billing using Eclipse?
Unfortunately I don't think there is any way to step debug, I have just been using print outputs. This is due to the fact that you have to sign your app with a release key in order for it to communicate properly with the billing service. Very annoying.
When you go through the in app billing documentation, you kinda realize that it can take substantial amount of time to understand this complex piece of technology. Most developers feel the need for a working HelloWorld, and then later play around with the builds.
I have uploaded 2 projects
The android sample project. You can download this project, and immediately run the sample. This will help you quickly debug/trace thru and figure out how the in app billing works.
A cleaned up project to help you integrate your app quickly. This can help like a library. Just integrate make your “purchase requests” on your “checkout” button action.
Mind you : I have not incorporated the security recommendations. Read android in app billing documentation. Until then you are on your own risk.
For 1
Download “http://www.4shared.com/file/f5wH3qke/InAppBilling1.html”
Create a new gmail account for all correspondence (Why, I will explain below)
Pay that 25$ and purchase a “Market Place” account.
Import the project to your eclipse environment
Create a signed application apk, File-Export-Select Your Project-Create OR Use keystore, it should be valid for 25 years from today.
Upload the signed apk to the market place as a “Draft Application”, DO NOT PUBLISH it.
For the uploaded apk, you need to add “In App Products”. You will find this link on the home page for your uploaded apk.
In Security.java dont forget to add your “public key” from your market place account “edit profile” page.
On the “In App Product List”, you need to add the following products one by one
The text below should used as “In app Product id”
sword_001 as Managed
potions_001 as Unmanaged
Title and Description dont matter (for testing purpose). Add what you need here.
Cost add 1$ (minimum)
Click auto fill
Save
Publish the in app project (dont get confused here, you only need to publish the in app product, NOT the APP)
In the test account, add your personal gmail id here. Now, this gmail account needs to be configured as your first gmail account on your phone.
Yes, this WONT work on your emulator
Now the sample app should work.
For 2
Download “http://www.4shared.com/file/h8YnJyf_/InAppBillingIntegration.html”
To integrate, in your calling activity initialize the checkout code
Handler handler = new Handler() ;
CheckoutPurchaseObserver checkout = new CheckoutPurchaseObserver(this, handler);
To send the checkout request for your product
checkout.sendCheckoutRequest(purchaseUri.toString(),null);
Important Note :
This purchaseUri is the “In-app Product ID” of your resource on the “market.android.com/publish-->Create New In-App Product” options. This string should be set as the “in app product” id.
That’s why the “id” is most important. The “In-App Product ID” is how you refer to that particular product.
Also, in Security.java dont forget to add your “public key” from your market place account “edit profile” page.**
Debugging Notes
LogCat will show all errors as InAppBilling tag
This project creates a shared_preferences named “inappbilling” And debug is set to true
The androidmanifest.xml may not be needed since this project does not
have a home screen.
Why do we need to create a new gmail account ?
Simple. The account you purchase your market place account for, cant be used for “testing” your in app billing. Since you cannot purchase products for yourself. And your primary account on your device should be set as a “test account” on the market place account. Chicken-Egg issue here. Hope its clear.
An interesting blog I came by “http://crazyviraj.blogspot.com/2011/06/some-notes-on-implementing-in-app.html“ (not mine).
In my app, I used the test product id, android.test.purchased, which will simulate the actual buying process (ie, will show the in app dialog and you'll be able to purchase and get a response that can be handled by your application). Using that product id, you can run the in app code on the device (unsigned) via eclipse over usb connection. You still might need to work around some things for testing (ie, account for the fact that you are using a testing product id and not your real id), but I found using that product ID did help me quite a bit.
See the testing section of the in app billing guide