Click Admob is not work

477 views
Skip to first unread message

赵佳亮

unread,
Jul 18, 2016, 4:42:07 AM7/18/16
to Google Mobile Ads SDK Developers
I meet a admob bug, sometime is not invoke startActivity for go to GooglePlay when I first click.
But it will be fine , when i click again.
Do you meet the same problem? Can you help me?

PS: I have encountered a bug that click admob is not work. The reason is i have two process.

Vu Chau (Mobile Ads SDK Team)

unread,
Jul 18, 2016, 4:49:51 PM7/18/16
to Google Mobile Ads SDK Developers
Hi there,

I'm not sure I understand the issue here.  Are you saying the clickthrough doesn't work when you tap on the ad? Do you have a screenshot/video that demonstrates this?

Vu Chau
Mobile Ads SDK Team

赵佳亮

unread,
Jul 19, 2016, 3:08:24 AM7/19/16
to Google Mobile Ads SDK Developers
Hi Vu
  Thanks for you help.The attach file is a small video. You can see that Ad jump to Google Play until I click twice. The first time is not work, and it is ok when i click again.
  And I pass a special Context that will print log when call startActivity to Admob SDK. The log reveal it's not call startActivity for the first time.
  And the bug is not always to show. Frequency is three to four times
device-2016-07-19-121540.mp4

Vu Chau (Mobile Ads SDK Team)

unread,
Jul 19, 2016, 10:37:47 AM7/19/16
to Google Mobile Ads SDK Developers
Hi there,

Thanks for the video! It was really helpful.

I haven't seen this behavior before.  So we will want to reproduce it locally to troubleshoot.  
Could you provide us additional details, such as the ad unit ID (if you can reproduce the issue in our sample), or some code snippets (if the issue is unique to your implementation)?
Also, which version of the SDK are you seeing the issue with?

Vu Chau
Mobile Ads SDK Team

Message has been deleted

Albert Snow

unread,
Jul 20, 2016, 5:19:54 AM7/20/16
to Google Mobile Ads SDK Developers
Hi Vu
  I think the issue is unique to our implementation. And I  cant to offer the apk. I will try by myself. 
  I want to debug the program, to figure out where the code to decide startActivity. But I get a problem when debug. Just like the screen shot, I can't get the class of com.google.android.gms.ads.internal.overlay.ai  ;   And I pretty sure the child view already handl the touch event. It just not call the method of startActivity
  Anyway, thanks for you help.
  

Albert Snow

unread,
Jul 21, 2016, 8:31:24 AM7/21/16
to Google Mobile Ads SDK Developers
Hi  Vu 
  We found some clue about the bug. 
  If we click the AD within about one second, it may not work. But i will be fine if i wait more longer time to click ad. 
  And if i click twice, it must work.
  So , I want to ask It's there have some policy to limit ad click event. Maybe about time and click times.

Vu Chau (Mobile Ads SDK Team)

unread,
Jul 21, 2016, 9:01:46 PM7/21/16
to Google Mobile Ads SDK Developers
Hi there,

Thanks for doing the extra testing.  Indeed there is a delay of about 150ms to avoid accidental clicks from occurring.  In real life use cases, most (if not all) users would first engage with the ad before clicking on it to learn more about the product.  

So I would say what you saw is not a bug.  If you have some other logic wired up that relies on the ad being clicked, you should ensure it's only active after the 150-ms delay.

Let us know if you have any questions,

Vu Chau
Mobile Ads SDK Team

Message has been deleted
Message has been deleted

Albert Snow

unread,
Jul 22, 2016, 6:26:15 AM7/22/16
to Google Mobile Ads SDK Developers
Hi Vu:
 I deleted the wrong post. I was clicked Tab, space bar....... Post be deleted...../(ㄒoㄒ)/~~。
 Anyway i will post the wrong delete post at the tail.
 Seriously, I found the reason of another bug. You can see that from the video. It's a chrome bug, and It's happen on occasion in specify device (e.g  Nexus 5X Android N, 6.0).
 
------------delete post--------------------------------------------------------------------------
  Thank you, It's really helpful ~\(≧▽≦)/~.  So there are some time limit, But, Are you sure the double click is also the limit?  And the 150s it's begain from ad view show in the screen, right?
  /(ㄒoㄒ)/~~   And we meet another bug........Sometime we click the ad, it's not go to Google Play. But it already start the Activity of com.goole.android.gms.ads.AdActivity.
  So, I guess there are some logic to stop jump Google Play.  It's will be very nice if there have some documents tell us the policy.
  I will continue to trace the bug............ Thanks for your patience.
------------------------------------------------------------------------------------------------
chrome_bug.mp4

Vu Chau (Mobile Ads SDK Team)

unread,
Jul 22, 2016, 1:41:04 PM7/22/16
to Google Mobile Ads SDK Developers
Hi there,

As far as I know, there is no limit imposed on the number of clicks.  
About when the 150ms starts to kick in, I won't be able to comment on that. 

Regarding the new issue, would you be able to open a separate thread for it?  While you're at it, could you tell me more about the implementation? It looks like you are showing the ad on the lock screen, is that correct?  The SDK doesn't support this use case, so that might be why the clickthrough doesn't fully work.

Vu Chau
Mobile Ads SDK Team

Vu Chau (Mobile Ads SDK Team)

unread,
Jul 22, 2016, 1:42:27 PM7/22/16
to Google Mobile Ads SDK Developers
As far as I know, there is no limit imposed on the number of clicks. 

However, there is a penalty for excessive invalid clicks on live ads. 

Albert Snow

unread,
Jul 25, 2016, 9:15:13 AM7/25/16
to Google Mobile Ads SDK Developers
Hi Vu:
  You are right, it's a locker app. We have two kind of process, one is application name to configure some thing, another is ***:locker name. 
  We have two plan for make a locker. 1. We have overlay permission, we make a view add to Window Manager from service as a locker. 2. No permission, we make Activity as a locker.
  In manifest, AdActivity is android:process=":locker".So there no process problem.
  
  And, we found the issue is not belong to chrome. The reason is AdActivity not start chrome. You can see the log at attachment.
  I use the command "adb logcat | grep "ActivityManager" to filter log. The first time click ad is work,  you can see the process: -------->AdActivity----->com.google.android.apps.chrome.Main. But the second time: ----->AdActivity,  it's end up with start AdActivity.
  I think maybe it's because of overlay. But i found the issue still happen when i use activity as a locker.
  
  So, do you know why AdActivity not start Chrome.
  
  So thanks for your help and patience O(∩_∩)O~. I know my English grammar is very bed....
issue.txt

Albert Snow

unread,
Jul 25, 2016, 9:39:24 AM7/25/16
to Google Mobile Ads SDK Developers
Hi Vu:
  Sorry, my test have some problem. I'm not test click Ad from Activity. It's still from overlay.
  So, I can't exclude the reason that we use WindowManager to make this issue. I will continue to test for the problem.

Vu Chau (Mobile Ads SDK Team)

unread,
Jul 25, 2016, 12:50:32 PM7/25/16
to Google Mobile Ads SDK Developers
Hi there,

I'm not sure if we are on the same page here.  To establish expectations, the SDK currently does not support lockscreen use cases.  If an issue arises out of that, it would be out of scope for the support we provide.

Let us know if you continue seeing any issue after further testing.

Vu Chau
Mobile Ads SDK Team

Reply all
Reply to author
Forward
0 new messages