Re: [google-admob-ads-sdk] Digest for google-admob-ads-sdk@googlegroups.com - 25 updates in 16 topics

436 views
Skip to first unread message

Aut Jaroenrit

unread,
Jan 10, 2018, 12:40:13 PM1/10/18
to google-adm...@googlegroups.com

เมื่อ 11 ม.ค. 2018 00:33 <google-adm...@googlegroups.com> เขียนว่า
"Gürkan Çatak" <gurkanca...@gmail.com>: Jan 10 09:25AM -0800

How to concact Product Support Team? Is there any form or e-mail to contact
them? I could not find any e-mail or form to contact.
 
 
28 Kasım 2017 Salı 00:09:03 UTC+3 tarihinde Deepika Uragayala- MobileAds
SDK team yazdı:
mobileadssdk-advisor+support@google.com: Jan 10 05:23PM

Hi,
 
Yes you should not hold an increasing number of NativeAds in memory, as
they are also somewhat memory intensive. For example, they also hold a
reference to a webview.
 
You cannot recycle NativeAds as such, so I suggest just having a limited
size data object (eg Array) to hold a limited number of native ads, and
remove the least recently used ad when a new ad needs to be added and the
data object has reached its capacity.
 
Regards
 
Sam
 
On 01/09/18 16:25:01 newr...@teamblind.com wrote:
 
Hi,
 
Thank you for the answer.
 
Let me ask you one more thing.
 
We have already recycled NativeAdView (NativeContentAdView,
NativeAppInstallAdView) in RecyclerView.ViewHolder.
 
Just the same problem occurs.
 
We update the RecyclerView by calling the AdLoader.load method and adding
the received response (NativeAd) to the RecyclerViewAdapter.
 
Should I also manage the NativeAd instance used in the RecyclerViewAdapter?
 
 
 
2018년 1월 9일 화요일 오전 10시 51분 53초 UTC-8,
mobileadssdk-a...@google.com 님의 말:
 
 
Hi,
 
Thank you for the sample project.
 
The issue you have highlighted here is not the SDK, but the sample app
implementation. The memory pressure is gradually increasing because there
is no recycling of the NativeExpressAdViews, so the further you scroll, the
more ad views are created, and since these are not lightweight objects, this
increases memory use quite substantially.
 
Thank you for highlighting this, the solution is to recycle a limited
number of ad views using the RecyclerViewAdapter for example, and this
would result in a finite memory consumption. The sample app being a fairly
simplistic example does not do such recycling.
 
Regards
 
Sam
 
On 01/08/18 13:15:30 newr...@teamblind.com wrote:
 
Hi
 
Add sample project.
 
Click 'Auto Scroll' button.
 
Crash after 3 to 5 minutes on Pixel device. Sometimes ANR reproduces.
 
Thank you.
 
https://drive.google.com/file/d/1FwkWyqfXo617sPwEdSDL1LJ3L7GHy
mnF/view?usp=sharing
 
2018년 1월 4일 목요일 오후 9시 39분 39초 UTC-8, Joshua Lagonera (Mobile Ads
SDK Team)
님의 말:
 
Hi there,
 
The SDK does use webviews to render ads. Can you check if you can replicate
the same behavior on our sample apps
<https://github.com/googleads/googleads-mobile-android-examples/tree/master/java/advanced>
so
we can rule out any implementation issues? Additionally, can you provide to
us a sample project we can use to replicate the issue in case it is not
reproducible using our sample apps? Kindly provide to us the appropriate
steps in replicating the behavior as well. You may also use the *Reply
Privately to Author* if you are not comfortable sharing your sample project
publicly.
 
Regards,
Joshua Lagonera
Mobile Ads SDK Team
 
On Friday, January 5, 2018 at 9:54:51 AM UTC+8, Dol Jobs wrote:
 
 
Load AdMob (NativeAd) into RecyclerView.
 
The ad is a separate ViewHolder.
 
A lot of scrolling (stress test) crashes.
 
Calling the destroy method on the NativeAd of the response will produce the
same result.
 
Is using AdLoader.load () to use webview internally?
 
 
01-04 17:41:54.038 A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** ***
*** *** *** ***
01-04 17:41:54.039 A/DEBUG: Build fingerprint:
'google/sailfish/sailfish:8.1.0/OPM1.171019.011/4448085:user/release-keys'
01-04 17:41:54.039 A/DEBUG: Revision: '0'
01-04 17:41:54.039 A/DEBUG: ABI: 'arm64'
01-04 17:41:54.039 A/DEBUG: pid: 24409, tid: 24409, name: ind.blind.debug
>>> com.xxx <<<
01-04 17:41:54.039 A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault
addr --------
01-04 17:41:54.045 D/WificondScannerImpl: Filtering out 86 scan results.
01-04 17:41:54.050 A/DEBUG: Abort
message: '[FATAL:aw_browser_terminator.cc(77)]
Render process (24702)'s crash wasn't handled by all associated webviews,
triggering application crash.
'
01-04 17:41:54.050 A/DEBUG: x0 0000000000000000 x1
0000000000005f59 x2 0000000000000006 x3 0000000000000008
01-04 17:41:54.050 A/DEBUG: x4 6e716761ff083963 x5
6e716761ff083963 x6 6e716761ff083963 x7 7f7f7f7f7f7f7f7f
01-04 17:41:54.050 A/DEBUG: x8 0000000000000083 x9
39d8b2c4cc595b96 x10 0000000000000000 x11 ffffffffffffffff
01-04 17:41:54.050 A/DEBUG: x12 0000007ffe3c3234 x13
0000007ffe3c322a x14 000000732ee02b7d x15 0000000000000054
01-04 17:41:54.050 A/DEBUG: x16 0000005a34fb9fa8 x17
00000073c44b1430 x18 0000000000000009 x19 0000000000005f59
01-04 17:41:54.050 A/DEBUG: x20 0000000000005f59 x21
0000000000000083 x22 000000732f64c000 x23 00000073c6640a40
01-04 17:41:54.050 A/DEBUG: x24 000000730d5cb000 x25
000000730d5cba18 x26 0000007ffe3c3818 x27 000000732edfed69
01-04 17:41:54.050 A/DEBUG: x28 000000732edfed75 x29
0000007ffe3c3300 x30 00000073c4464a2c
01-04 17:41:54.050 A/DEBUG: sp 0000007ffe3c32c0 pc
00000073c4464a4c pstate 0000000060000000
01-04 17:41:54.054 A/DEBUG: backtrace:
01-04 17:41:54.054 A/DEBUG: #00 pc 000000000001da4c
/system/lib64/libc.so (abort+112)
01-04 17:41:54.054 A/DEBUG: #01 pc 000000000076b0d8
/data/app/com.android.chrome-iextVbdNj6XrNy5ldoFD6Q==/base.apk (offset
0xb86000)
 
I don't speak english. so used google translate service.
 
Sorry about that.
 
--
 
---
You received this message because you are subscribed to the Google Groups
"Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/google-admob-ads-sdk/0413ba8d-c567-41ae-8914-
f9cf51a1e46a%40googlegroups.com
<https://groups.google.com/d/msgid/google-admob-ads-sdk/0413ba8d-c567-41ae-8914-f9cf51a1e46a%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
 
--
 
---
You received this message because you are subscribed to the Google Groups
"Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-admob-ads-sdk/ced342a1-9b98-41fd-ae7f-254a808c8cf1%40googlegroups.com
<https://groups.google.com/d/msgid/google-admob-ads-sdk/ced342a1-9b98-41fd-ae7f-254a808c8cf1%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
Rafael Lossurdo <loss...@gmail.com>: Jan 10 06:53AM -0800

Maybe I have received an e-mail saying I had to accept the new Terms of
Service but I'm not sure of that.
Today I tried to sign in my Google Account on https://apps.admob.com and it
says my administrator (that it is me) has not accept the terms of
service... and my access were revoked.
I have an active app running and it is presenting ads... so it is still
working.
 
Does anyone know how to unlock my access or accept those Terms?
Gold Locke <szodr...@gmail.com>: Jan 10 06:23AM -0800

Hi,
 
I understand, every app has an app ID. Must I put this app ID in the app or
is it enough only to put in the ad unit ID?
I put in only the ad unit ID and have no problems. So must I put in the app
ID? Or do I have to put it only to have some features with firebase?
Question is, is it important or not?
 
Can I put the app ID in string.xml, like <string
name="admob_app_id">ca-app-pub-XXXXXXXX~XXXXXXXXXXX</string>?
 
Thank you in advance.
刚雷 <leiga...@gmail.com>: Jan 10 05:55AM -0800

Hello, I used my appid ca-app-pub-9993385829891821~2508172139 and unit ID ca-app-pub-9993385829891821/3418367468
to your sample app,but it always show *Reward based video ad failed to
load. please help me .*
 
On Monday, December 11, 2017 at 4:53:46 PM UTC+8, Ivan Bautista (Mobile Ads
SDK Team) wrote:
mudabbir.latif.technokeet@gmail.com: Jan 09 09:34PM -0800

I have attached my script for admob ads, please check it
mobileadssdk-advisor+support@google.com: Jan 10 07:05AM

Hi there,
 
Thank you for providing a sample code snippet showing your implementation.
Looking into it, there doesn't seem to be anything suspicious from an SDK's
perspective.
 
However, it looks like you are trying to programmatically obtain the Test
Device IDs. Kindly note that the *only* recommended way of obtaining the
Device ID to be used in the Ad Request is by obtaining it from the
console/logcat output
<https://developers.google.com/admob/unity/test-ads#add_your_test_device>.
This may be the reason why the "Test Ad" label is not showing on your end
since an incorrect Test Device ID will result in Live Ads showing.
 
I would suggest that you double-check the Test Device IDs that you are
using in your Ad Requests and make sure they are the same IDs that are
shown in the console/logcat.
 
Regards,
Joshua Lagonera
Mobile Ads SDK Team
 
On 01/10/18 13:34:56 mudabbir.latif.technokeet@gmail.com wrote:
 
I have attached my script for admob ads, please check it
 
--
 
---
You received this message because you are subscribed to the Google Groups
"Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-admob-ads-sdk/e14b93ac-ce86-4f27-9ffb-d59cd23cfb76%40googlegroups.com
<https://groups.google.com/d/msgid/google-admob-ads-sdk/e14b93ac-ce86-4f27-9ffb-d59cd23cfb76%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
mudabbir.latif.technokeet@gmail.com: Jan 10 01:57AM -0800

Hi,
Thanks for your reply but this way of getting device id is correct,it is
providing correct id and "Test Ad" label for video ads are working fine but
causing problem only in banner and interstitial ads
mobileadssdk-advisor+support@google.com: Jan 10 10:41AM

Hi there,
 
As previously mentioned, it is recommended that you use the Device IDs
shown on the console/logcat in your Ad Requests to ensure that you are
requesting for test ads properly. You may refer to our official guide
<https://developers.google.com/admob/unity/test-ads#add_your_test_device>
on how to properly request for Test Ads.
 
That said, can you try using the Test Device ID that was shown on the
console/logcat and see if you can still replicate the issue? Would you also
be able to provide to us the logs that is shown on the console/logcat so we
may be able to investigate further? Additionally, would you be able to
provide to us the logs from Charles' Proxy <https://www.charlesproxy.com/>
with
*SSL Proxying *enabled? You can refer to this document
<https://support.google.com/dfp_premium/answer/6206401> on how to properly
set it up.
 
Regards,
Joshua Lagonera
Mobile Ads SDK Team
 
On 01/10/18 17:57:23 mudabbir.latif.technokeet@gmail.com wrote:
 
 
Hi,
Thanks for your reply but this way of getting device id is correct,it is
providing correct id and "Test Ad" label for video ads are working fine but
causing problem only in banner and interstitial ads
 
--
 
---
You received this message because you are subscribed to the Google Groups
"Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-admob-ads-sdk/bf93328f-e18b-4a4a-8f3e-87fb2281c19b%40googlegroups.com
<https://groups.google.com/d/msgid/google-admob-ads-sdk/bf93328f-e18b-4a4a-8f3e-87fb2281c19b%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
Guanaco Devs <guana...@gmail.com>: Jan 10 12:36AM -0800

How can I customize the Dialog that pop ups when a user close the video
before it is finished.
Is it possible?
 
Best Regards
Edgard
mobileadssdk-advisor+support@google.com: Jan 10 09:21AM

Hi Edgard,
 
I'm afraid that customizing the popup is currently not possible for the
Mobile Ads SDK.
 
Let me know if you have any further questions.
 
Regards,
Joshua Lagonera
Mobile Ads SDK Team
 
On 01/10/18 16:36:18 guana...@gmail.com wrote:
 
How can I customize the Dialog that pop ups when a user close the video
before it is finished.
Is it possible?
 
Best Regards
Edgard
 
--
 
---
You received this message because you are subscribed to the Google Groups
"Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-admob-ads-sdk/00125943-00cf-4931-98ec-331b36d8f0ff%40googlegroups.com
<https://groups.google.com/d/msgid/google-admob-ads-sdk/00125943-00cf-4931-98ec-331b36d8f0ff%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
Guanaco Devs <guana...@gmail.com>: Jan 10 03:59AM -0600

Ok, thanks for the information.
 
Kyaw Soe Win <ksw...@gmail.com>: Jan 10 01:22AM -0800

Hi So Far my understanding is "if you are using Google play Services (Any
Version) in your app, you are save (you don't need to update your Google
play Services SDK) if your users have google play services library(Version
higher than 7.0) in their device." Am I correct?
Thanks
Kyaw
 
On Tuesday, 9 January 2018 01:17:06 UTC+6:30, Deepika Uragayala- MobileAds
SDK team wrote:
mengru ren <elaine...@gmail.com>: Jan 09 11:57PM -0800

Hello Team,
 
I've implemented Native Advance Ad with a test unit ID, and I insist on
creating a new unit ID for Native Advance Ad. Next, I was prompted to
contact Google's account manager to create a unit ID for a native ad, but
how do I get in touch with my client's google account manager?
mobileadssdk-advisor+support@google.com: Jan 10 09:20AM

Hi there,
 
Kindly note that Native Advanced Ads are only available to a selected
number of publishers. You may contact our Product Support Team
<https://support.google.com/admob/contact/account_setup> if you wish to
participate in the Native Advanced beta and contact an Account Manager.
 
If this is not applicable to you, then I would suggest that you follow our
official blog <https://admob.googleblog.com/> for official news and
announcements regarding AdMob.
 
Regards,
Joshua Lagonera
Mobile Ads SDK Team
 
On 01/10/18 15:57:41 elaine...@gmail.com wrote:
 
Hello Team,
 
I've implemented Native Advance Ad with a test unit ID, and I insist on
creating a new unit ID for Native Advance Ad. Next, I was prompted to
contact Google's account manager to create a unit ID for a native ad, but
how do I get in touch with my client's google account manager?
 
--
 
---
You received this message because you are subscribed to the Google Groups
"Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-admob-ads-sdk/3eccf4c4-fadb-4622-83f5-f8bbb2b0e972%40googlegroups.com
<https://groups.google.com/d/msgid/google-admob-ads-sdk/3eccf4c4-fadb-4622-83f5-f8bbb2b0e972%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
"張路欣 Lucia.Chang" <lucia.chang@nextanimation.com.tw>: Jan 09 08:42PM -0800

Hi!
 
Not sure if this is the right place, but I've noticed that my app has
stopped serving ads completely since September 5th, 2017.
I'm unable to see any reports after that date.
 
I have an Android & iOS app, and each app has 4 ad units that the Admob
backend displays as "active" at the moment.
 
The ad unit ID for one of the Android ones
is ca-app-pub-1672336589828297/3311499962
 
Thank you.
 
 
 
 
 
--
免責聲明 http://disclaimer.nextanimation.com.tw/
mobileadssdk-advisor+support@google.com: Jan 10 06:38AM

Hi,
 
I have to re-post your original concern as it contains your Ad Unit Id
which is considered as confidential information. Moving forward, please
avoid posting confidential information in the public forum.
 
That said, below is a copy of your original post with the masked
information.
 
Hi!
 
Not sure if this is the right place, but I've noticed that my app has
stopped serving ads completely since September 5th, 2017.
I'm unable to see any reports after that date.
 
I have an Android & iOS app, and each app has 4 ad units that the Admob
backend displays as "active" at the moment.
 
The ad unit ID for one of the Android ones is ca-app-pub-
XXXXXXXXXXXXXXXX/XXXXXXXXXX
 
Thank you.
 
 
Regards,
Ivan Bautista
Mobile Ads SDK Team
mobileadssdk-advisor+support@google.com: Jan 10 06:41AM

Hi,
 
I tested your Ad Unit Id with our sample app
<https://github.com/googleads/googleads-mobile-android-examples/tree/master/java/admob/BannerExample>
and
I kept on getting No fill error. Even with an enabled test device
<https://developers.google.com/admob/android/test-ads#enable_test_devices>,
I'm still getting the No fill error which is out of the ordinary. That
said, this seems to be more of an Ad serving issue rather than anything
specific to the Mobile Ads SDK. I suggest that you have this Ad Unit Id
double checked by the Product Support Team
<https://support.google.com/admob/v2/contact/account_setup> as they can
look further into this and give you more insights.
 
Also, you may use this Troubleshooter
<https://support.google.com/admob/troubleshooter/6401922?hl=en> for
additional assistance.
 
Regards,
Ivan Bautista
Mobile Ads SDK Team
Jeffrey Chen <jche...@gmail.com>: Jan 09 09:27PM -0800

I am having the same issue, and I created an example application where I
can replicate it consistently: https://github.com/jchen1352/AdMobBug
The problem is in RewardedVideoAd.destroy, since removing that fixes the
problem.
 
On Friday, May 26, 2017 at 4:05:28 AM UTC-7, Steven Haggerty wrote:
"Joshua Lagonera (Mobile Ads SDK Team)" <mobileadssdk-advisor+joshua@google.com>: Jan 09 10:40PM -0800

Hi Jeffrey,
 
Thank you for providing an example application. I can confirm that I am
also able to replicate the issue consistently using it, as well as the
sample steps you provided.
 
I'm going to forward this information to the rest of the team and get back
to this thread for updates regarding this issue.
 
Regards,
Joshua Lagonera
Mobile Ads SDK Team
 
On Wednesday, January 10, 2018 at 1:27:12 PM UTC+8, Jeffrey Chen wrote:
mobileadssdk-advisor+support@google.com: Jan 10 04:28AM

Hi Idriss,
 
I'm afraid we can only assist you with technical concerns specific to the
code implementation of the Mobile Ads SDK. It's best that you reach out to
the Product Support Team
<https://support.google.com/admob/contact/account_login_issues?hl=en&cfnti=6142968&cft=3>
as
they are the appropriate team to assist you on this.
 
Alternatively, you may refer to this article
<https://support.google.com/admob/answer/7356424?hl=en> for relevant
information about Sign-up errors or use this Troubleshooter
<https://support.google.com/admob/troubleshooter/3168090> for additional
assistance.
 
Regards,
Ivan Bautista
Mobile Ads SDK Team
"Ivan Bautista (Mobile Ads SDK Team)" <mobileadssdk-advisor+ivan@google.com>: Jan 09 08:26PM -0800

Hi Raviraj,
 
Thank you for testing it out with our sample apps
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fgoogleads%2Fgoogleads-mobile-android-examples%2Freleases%2Ftag%2F5.0&sa=D&sntz=1&usg=AFQjCNE3LgwjaxIHv3b1HQzCvi0FykiaSw> and
for sharing with us your findings privately. Since you were able to display
test ads in your app, then the issue is not with your code implementation
of the Mobile Ads SDK. Since you were able to display ads when testing your
Ad Unit Id with our sample app, then this seems to be more of an Ad serving
issue.
 
If you suspect that one of your accounts or apps were disabled, then it's
best that you have this checked by the Product Support Team
<https://support.google.com/admob/contact/account_setup> as they can
further look into this. You may also use this Troubleshooter
<https://support.google.com/admob/troubleshooter/6401922?hl=en> for
additional assistance.
 
Regards,
Ivan Bautista
Mobile Ads SDK Team
Rahul Kumawat <rkuma...@gmail.com>: Jan 10 09:56AM +0530

Hello Deepika
 
Now Issue has resolved. Thanks for your support.
 
Thanks & Regards,
Rahul Kumawat
 
On Wed, Jan 10, 2018 at 1:58 AM, 'Deepika Uragayala- MobileAds SDK team'
via Google Mobile Ads SDK Developers <google-admob-ads-sdk@googlegroups.com>
wrote:
 
黄冬 <huangdon...@gmail.com>: Jan 09 06:33PM -0800

OK. Thank you.
 
On Tuesday, 9 January 2018 23:20:38 UTC+8, Bharani Cherukuri (Mobile Ads
SDK Team) wrote:
"Ram Parameswaran (Mobile SDK Team)" <mobileadssdk-advisor+ram@google.com>: Jan 09 06:28PM -0800

Although this issue does seem to affecting a wide variety of Amazon
devices, I cannot conclusively say all devices are affected. This issue has
been escalated internally and the ad serving team working towards resolving
the issue as soon as possible.
 
- Ram
 
On Tuesday, January 9, 2018 at 2:07:34 AM UTC-8, Ta-Dah Apps wrote:
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to google-admob-ads-sdk+unsub...@googlegroups.com.

Aut Jaroenrit

unread,
Jan 10, 2018, 12:42:10 PM1/10/18
to google-adm...@googlegroups.com

Aut Jaroenrit

unread,
Jan 10, 2018, 2:56:48 PM1/10/18
to google-adm...@googlegroups.com

เมื่อ 11 ม.ค. 2018 00:41 "Aut Jaroenrit" <rauyk...@gmail.com> เขียนว่า

เมื่อ 11 ม.ค. 2018 00:33 <google-admob-ads-sdk@googlegroups.com> เขียนว่า

To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/google-admob-ads-sdk/0413ba8d-c567-41ae-8914-
f9cf51a1e46a%40googlegroups.com
<https://groups.google.com/d/msgid/google-admob-ads-sdk/0413ba8d-c567-41ae-8914-f9cf51a1e46a%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
 
--
 
---
You received this message because you are subscribed to the Google Groups
"Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
"張路欣 Lucia.Chang" <lucia...@nextanimation.com.tw>: Jan 09 08:42PM -0800
To unsubscribe from this group and stop receiving emails from it send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages