I want to coding for auto click on ads for the android studio, I mean when interstitial ad show then auto click on it.I know this is against the AdMob but I want to try this only for study purpose.Please Help me.
Well, even if you do this you'll receive nothing as you're account will get banned as you're using a bot to automatically and illegally clicking on ads to receive reward.
About Rewards, you will receive nothing there too, because those clicks will be counted as Accidental Clicks.
So better to create a good app with good UI and publish with ads and earn rewards.
Have A Nice Day ! š
Its absolutely against admob policy. You account might be suspended if detected. Yes you can create a bot that can click on the ad links but you wont get any revenue. Because admob can detect whether its a human click or bot click. From single device you wont get revenue.
Easy secret behind high revenue from admob is high active install and high usage of the app.
Related
I am new to AdMob and I am using banner add in my android application. test adds were working perfectly but now real adds are not showing. Now I received an Email from AdMob that
Thank you for your interest in AdMob. After reviewing your application, our specialists have found that it does not meet our program criteria. Therefore, we are unable to accept you into our program.
But I am not violating any of there policy. Why is this happening and what is a solution now?
I created chrome extension, uploaded into my new google developer account and tried to pay for one-time developer registration fee, but when I click into 'Pay now (5USD)' button and then into Buy button in 'Complete your purchase' modal window, then nothing happens. I tried to do it many times (also from firefox ;). Console shows: GET https://224.32.32.161/13161 net::ERR_ADDRESS_INVALID.
screen: https://i.imgur.com/Afz7Bpo.png
I tried to contact with google, but with no success.. :/
I was able to reproduce your issue in a vanilla Chrome.
I would suggest to inform them about this issue here:
https://support.google.com/chrome_webstore/contact/developer_support
Initially, I built up a test agent on DialogFlow console according to the document, and it works well on the Actions On Google which is a simulator of Google Assistant on mobile devices.
Then, I deployed it through the Release in the left menu as you can see the pic attached.
deployed successfully
After that, I added some Alpha Testers including my colleague and sent my opt-in link to my colleague, besides, I granted them all the viewer permission in IAM.
However, problem appeared. It didn't work well on my testersā phone(IOS 10+) but only worked well on developer's account(mine). When they opened the link I sent to them, and clicked send to devices, then clicked the notification on top of the screen.
send to device
The result is shown as below.
Google Assistant didn't respond to "Talk to mytest app"
In my case the command was set as "Talk to hello qad", and it did work well on my phone used the developer account.
developer account works well
If my tester input the text "Talk to hello qad", it just replied some direct searching results not hello qad diaglog.
To recap:
My action has already been in "deployed" status for couple of days
I've added the tester accounts in whitelist and give them "Viewer" permission in IAM
Testers could see the action directory page in devices by open opt-in link, but they couldn't see the "I'm In" button and couldn't access the action
Appreciate for any help or advice
During my project development, I also faced a similar issue. This is how managed to do testing:
Made sure all Google Accounts were created with the US as the country.
Through IAM, share AoG project with the tester's Google accounts.
All testers to open the shared simulator link in their browsers. This is important!
Test the app on browser first using the simulator.
Once tested, use any device with the whitelisted Google Accounts.
US country was required for my use case as I was having Transaction API in my Assistant. I had to also mock my location to the US on mobile for testing US specific features.
See if the above steps help you.
I contacted Google and this is what they said:
You have to copy the link to the notes app, and then click it and in the prompt, choose āOpen in Assistantā.
Full text:
Please ensure that the opt-in link is opened in Google Assistant app and not in a browser.Ā At this time, Google Assistant app is only available in USA.Ā For opening an opt-in link inĀ iPhoneĀ or any iOS device,Ā please follow the steps below:
1. Download the Assistant App in App Store
2. Log in using the included account for Beta testing
3. Copy the opt-in URL to Notes app
4. Hold press the opt-in link then selectĀ 'Open in "Assistant"'.Ā Google Assistant and App page in the Assistant Directory will be displayed.
5. Scroll down the page until you see the "Become a Beta tester" section
6. ClickĀ theĀ I'M INĀ button
7. Test the Action
This does not work for me, probably because I am not in the US. However, the app is of course available here.
I ran into a similar issue with Google Actions/Dialog Flow. Here is how I resolved it...
Share the app from within DialogFlow to the test user
Copy the current DialogFlow URL from the address bar
Launch an Incognito Window
Paste the DialogFlow URL from Step 2 in the address bar
Log into DialogFlow using the test account
At the Standard Google Account Access Prompt Allow the access so your Google Action can talk to DialogFlow.
I couldn't find this documented anywhere and wasted about 8 hours figuring it out.
For me it only worked after I shared with the user the link to test on desktop that look likes: https://console.actions.google.com/project/XXX/simulatorcreate?isDeepLink the one you can get the the console menu on the sharing icon.
I asked him to login with same google email he has opted-in in Google Assistant and
to verify if when mouse over on the devices icon on the menu he would see "Testing on Device: Enabled
You currently are able to test your Actions on all
Assistant devices connected to "xxxx#gmail.com". "
Then he could invoque almost right away the alpha version of the BOT.
All that considering that he has already clicked on the opt-in link, I had added his emails as a Alpha tester and I had also added him as a Viewer on Permissions at the console admin https://console.cloud.google.com/iam-admin.
If you are a developer of the project, the test version is enabled by default on your device. If you want to access the alpha and beta versions, make sure to disable the āTesting on deviceā option on the Actions Console simulator.
Add users before deploying alpha release
I feel obligated to copy dedman's comment on your question here, since his solution worked for me and is the only one directly addressing the problem at hand: an alpha release is not available to testers you have added after deploying the release.
As stated in question, you first deployed the test version and then added alpha testers. You might have to publish new alpha version "after adding the testers" and then wait till you get "deployed" status on the new alpha release too... ā dedman
I was encountering this exact problem with the Alpha release of my Action, i.e. assistant not responding on alpha users devices, even though I had deployed the release, shared the opt-in link with users and had them click on it to opt-in. Deploying a new alpha release after users had clicked the opt-in link solved the problem and the action is now responding correctly for all users.
IAM Viewer status is not mandatory
By the way, I can also confirm your suspicion that "Viewer" permission in IAM is not needed for alpha users to have access to your release - they only need to opt-in before you deploy a new release.
I have never deployed an app for texting in a real iOS device, only on an iPhone 7 plus simulator. I've watched some tutorials on how to do it and this is what I have done so far.
I have made an iOS Development Certificate. I made an App id, connected a device and entered the UDID. Then created a new device and at last I have made a Provisioning Profile with the iPhone 7 Device connected. The iOS development certificate connected and the App ID connected. After I did all of that, I continued to watch all the tutorials but there seems to be a change which I can't figure out.
As you can see, in the picture above there is a view detail button which you click then download your Provisioning Profile to your XCode, but for me there is no View Detail button. Instead it looks something like this.
So unfortunately, I don't know what to do from here. I tried going to Xcode > Window > Devices then right clicked on my device then it looks something like this.
So I click Show Provisioning Profiles, press "add" then add my Provisioning Profile. The next thing I did was go back to Xamarian went to info.plist, double clicked it and then entered my Bundle Identifier.
Then right clicked the 2 Calculator file, went down to Options and then set everything up, as you could see in the picture. Then I press run but it doesn't seem to work
This error message comes up:
I am pretty sure I have done everything right, but there seems to still be an error. The only possible bit I think may have gone wrong is when there wasn't the "view detail" button, so I did it a another way. Maybe the problem is I downloaded the Provisioning Profile on the iOS Device, but not in the Xcode mac or something?
I don't have a clue what I did wrong and have tried everything about 5 times but it still didn't work. It will be great if someone could help.
These are all the Certificate and stuff I did in the App development section.
Not enough reputation to comment, so I am going to take a shot in the dark here. My question to you is, did you download the certificate to your MacBook before or after you added your mobile device to it? Your Mac has to know of which devices you have allowed to develop on, so you need to make sure your .mobileprovision on your Mac has that UDID in it.
You can check if your .mobileprovision is added by looking in "~/Library/MobileDevice/Provisioning Profiles" and sorting by "Date Modified" to see if you have a fresh one updating after you downloaded it from developer.apple.com. Xcode will assign a GUID to the name so the provisioning profile will not have the name displaying on the website.
Also, the error possibly looks certificate related. Is the certificate valid and trusted in your keychain? I noticed no mention of adding the certificate to the "Keychain Access" application.
Whn I try to upload my app, I get this error in Application Uploader "Application failed codesign verification. The signature is invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate.".
If I open MonoDevelop, properties and select "iPhone bundle signing", then I see a "Provisioning profile", but if I click another topic (eg Crash report) and go back to "Provisioning profile", then it suddenly says "Unknown" and a guid.
How do I tell MonoDevelop to use the correct Provisioning profile?
I deleted some old profiles (in Organizer), but they still show in MonoDevelop.
Unfortunately the "provisioning hell" created by the Apple signature system is made even worse in MonoDevelop.
There is no provisioning manager, no way to setup and associate all the provisioning profiles and the keys to a specific monotouch app. MonoDevelop lacks a wizard to automatically create or guide the user in the creation, download or backup of the right profiles, keys and appIDs.
The best way to know if a profile or a key is wrong, expired, incompatible with an appId, or rejected, is to check all of them manually in the XCode Organizer (you can find it in the XCode "Window" menu).
Once in Organizer, you need to go to click on the LIBRARY -> Provisioning Profiles section on the left, and then click on the Refresh button to synch your profiles with apple server (if you have those on file or you are on another dev computer and you have to install only selected profiles, click on the Import button and manually select the files).
Then you need to attach your ios device and when it appears in the DEVICE->your_iPhone_or_Ipad name.. you need to drag and drop the provisioning profiles that you need from the LIBRARY->Provisioning Profile to the DEVICE->your_iPhone_or_Ipad_name->Provisioning Profiles...
Many things can go wrong anyway, especially mixing old profiles with the new profiles supporting iCloud or some other advanced app features. There is no way to know if a bundle id is valid, if the entitlements are allowed, if a profile or an appID is enabled or not to use iCloud, Notifications, IAP, etc., or if it's registered for Developer, AdHoc or Distribution, and what product id strings it's compatible with. You need to go by trials and errors. Even the simple creation of an ad Hoc version of your app enabled for a trusted remote tester is a long and perilous road. There is no users and testers profiles manager in MonoDevelop, you need to remember what goes with who every time.
If you are on a different developer machine, you also need to install the registered developer keys in the local KeyChain (I suggest to do a backup of those keys somewhere: if you lose those keys, you will be unable to update your app in the future!!).
Let us hope that Xamarin will add a profiles and keys manager soon.
#Emanuale mentions alot, but he is going the long route on a lot of these.
There is a simpler way to go about everything. Here is the cut and dry approach:
Login to the provisioning portal on the web
Create an App ID for your company as "com.yourcompanyname.*"
Create a provisioning profile for this app ID for both development and distribution
(I would also recommend to delete any profiles you don't need)
Open XCode->My Organizer, and press the refresh button in the bottom right corner (you will see all your profiles from online appear)
Deploy your app to the device from MonoDevelop (make sure your bundle ID is com.yourcompanyname.yourappname)
This is the simplest way to go about this. No need to mess with provisioning profile settings in MonoDevelop, the defaults should work.
The only gotcha is if you need to support push notifications. The com.yourcompanyname.* profile won't work, you will have to make a profile specific to each app in this case.
Great answer jonathanpeppers! Just a 2c, now XCode->My Oganizer is Preferences->Accounts
If the accepted response doesn't help, you should also ensure that your Signing Identity matches the Provisioning Profile you're using, and that it has a private key. These can be switched up if you have multiple Signing Certificates installed, and you won't be able to tell the difference from Xamarin Studio. See
https://stackoverflow.com/a/37856762/660194