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

230 views
Skip to first unread message

George Dela Pena

unread,
May 30, 2024, 5:48:36 AM5/30/24
to google-adm...@googlegroups.com
Hi,

I would like to check if there has been any progress or updates regarding the issue I reported earlier. Any information would be greatly appreciated.

Thank you. 

George Dela Pena

On Thu, May 30, 2024 at 11:26 AM <google-adm...@googlegroups.com> wrote:
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 07:56PM

Hi,
 
I will check with our team regarding your query and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ6SB:ref" (ADR-00236713)
 
Thanks,
 
Mobile Ads SDK Team
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 08:55PM

Hi,
 
Thank you for sharing the requested information.
 
I have performed the execution of the project you forwarded and am unable to load the ads on my end. However, the execution has resulted in the display of an error message "No ad to show". Upon further investigation, this seems to be a serving issue rather than something specific to the Mobile Ads SDK. The next step for you would be to reach out to the Product Support Team as they are better equipped to address your concern and provide further assistance.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ6SB:ref" (ADR-00236713)
 
Thanks,
 
Mobile Ads SDK Team
system fia <fia.sys...@gmail.com>: May 29 06:08PM -0700

Thank you for your reply!
 
I was told to contact the Product Support Team
<https://support.google.com/admob/community> , but the link was to the
Help Community.
Will asking a question here lead to Google's Product Support Team?
 
2024年5月30日木曜日 5:56:24 UTC+9 Mobile Ads SDK Forum Advisor:
 
system fia <fia.sys...@gmail.com>: May 29 06:24PM -0700

I contacted Google Support team.
https://support.google.com/admob/thread/277162771?hl=ja&sjid=17887676457304851635-AP
 
2024年5月30日木曜日 10:08:53 UTC+9 system fia:
 
"Szabolcs Négyesi" <yal...@gmail.com>: May 29 11:27AM -0700

I tried duplicate entry (it really accepts the same ID with all capical
letters as a separate device, which is quite ridiculous imho), but it did
not solve the problem.
And now I'm banned too.
I guess they screwed up something in the background, 'cause my test ads
were just fine until the end of April.
Do you have any tips about how could I fix this? (after I finally get my
account back...)
 
On Monday, May 6, 2024 at 4:27:21 AM UTC+2 Bence Menyhárt wrote:
 
Konstantin Shkulev <konstanti...@mytona.com>: May 28 09:39PM -0700

Hi! We are using the latest Google Mobile Ads SDK for Unity to obtain
consent from EU users via Google UMP. Our testers found a bug where
IABTCF_gdprApplies does not change its value when user moves out from EU.
 
Steps to reproduce:
1. Use VPN of EU country to fake your location
2. Launch game and gave consent in CMP window
3. Close game
4. Disable VPN (you must live outside EU) or use VPN of non-EU country
5. Launch game
 
In this case after updating ConsentInformation IABTCF_gdprApplies is still
set to 1 with ConsentStatus = Obtained and PrivacyOptionsRequirementStatus
= Required.
 
Is this a bug or a proper behaviour, like if user once applied to GDPR he
still be able to manage consent even if he lives outside of EU?
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 11:54AM

Hi,
 
Thanks for contacting us.
 
I am checking your concern and will get back to you shortly.
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ7RA:ref" (ADR-00236924)
 
Thanks,
 
Mobile Ads SDK Team
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 10:35PM

Hi,
 
It appears to be an intended behavior. According to the IAB, there is a requirement to display a consent pop-up for users in the European Economic Area (EEA), but no such requirement exists for users outside the EEA. If a user first logs in from a non-EEA location, all ads will be served. However, If the user declines consent, limited ads will be served.
 
If a user transitions from a non-EEA location to an EEA location, the IABTCF_gdprApplies flag will change and the user will be given the option to update their consent preferences. Conversely, if a user transitions from an EEA location to a non-EEA location, consent is no longer applicable and ads will be served normally. This is similar to the iOS ATT pop-up. If the user grants permission, ads will be served regardless of the user's location.
 
For debugging purposes, you can use the UMPConsentInformation reset method to reset the consent logic. This will reset the IABTCF_gdprApplies flag and all other consent-related settings.
 
To resolve your current issue, you should store the user's previous region in the device's defaults. If the user's previous region was the EEA and their current region is non-EEA, and the user has previously granted consent, you should reset the consent settings and proceed accordingly.
This should resolve your current issue.
 
Kindly get back to us if you need any other help related to Mobile Ads SDK.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ7RA:ref" (ADR-00236924)
 
Thanks,
 
Mobile Ads SDK Team
Koji Ono <worldv...@gmail.com>: May 29 02:15PM -0700

I can't find my iOS app from AdMob link
 
I released an app in the app store three days ago, but I can't link to it from AdMob.
 
URL of the app store:
https://apps.apple.com/us/app/auto-zoom-camera/id6498964013
 
Please help me.
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 10:27PM

Hi,
 
I understand that you are unable to link your app to AdMob. Please note that your app should be available on the app store, it may take 24 to 48 hours before you can link to it. In some cases, it may take up to one week. I have tried searching the app with provided URL and able to find your app in AdMob.
 
If you have any other concerns for the technical/implementations for Mobile Ads SDK, feel free to reach back to us so we can further assist you.
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ8Ft:ref" (ADR-00237068)
 
Thanks,
 
Mobile Ads SDK Team
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 09:30PM

Hi Maxter,
 
We acknowledged your previous communication and provided a response. However, it appears that the previous response was sent privately. Hence, we are reproducing the response below for your convenience.
 
Your app hasn’t been reviewed yet. To prompt a review, make sure your app has been verified and linked to a supported app store in AdMob. We could not load ads using the ID's that you have provided and couldn't find any issues mentioned in your AdMob dashboard.
 
Could you please confirm whether you have included following code in your project:
 
RequestConfiguration requestConfiguration = MobileAds.getRequestConfiguration()
 
.toBuilder()
 
.setTagForChildDirectedTreatment(
 
RequestConfiguration.TAG_FOR_CHILD_DIRECTED_TREATMENT_TRUE)
 
.setMaxAdContentRating(RequestConfiguration.MAX_AD_CONTENT_RATING_G)
 
.build();
 
MobileAds.setRequestConfiguration(requestConfiguration);
 
Please note that only skippable ads will be served in rewarded interstitial ad units. Do follow Comply with Google Play’s Families Policy using AdMob, Ads format requirements, Ads articles to be in compliance with AdMob policies.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ5Kb:ref" (ADR-00236408)
 
Thanks,
 
Mobile Ads SDK Team
talha rehman <talhareh...@gmail.com>: May 29 06:47AM -0700

Dear Google Support,
 
I am experiencing an issue with the ad functionality in my app on the iOS
platform. Specifically, when an interstitial ad is called and subsequently
closed, an App Open Ad is displayed immediately afterward. This behavior
disrupts the user experience, as the app should continue seamlessly after
the interstitial ad is closed.
 
Here are the details:
 
 
- Platform: iOS
- Issue: App Open Ad shows after closing the interstitial ad.
- Expected Behavior: The app should continue without displaying an App
Open Ad after the interstitial ad is closed.
- Steps to Reproduce:
 
 
1. An interstitial ad is called through a button.
2. An interstitial ad is displayed.
3. The interstitial ad is closed.
4. App Open Ad is displayed immediately afterward.
 
This issue is affecting the user experience on iOS, and I would appreciate
your assistance in resolving it. Please let me know if you need any
additional information from my side.
 
Thank you for your help.
 
Best regards,
 
Talha
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 08:51PM

Hi,
 
We have tried running Google sample project and unable to reproduce the mentioned issue. It seems to be an implementation issue. Can you recheck GADAppOpenAd load steps in your project. Kindly share below details via "Reply to author" option for further investigation:
 
app ID
ad unit ID
Sample project where the issue can be observed.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ7ww:ref" (ADR-00237037)
 
Thanks,
 
Mobile Ads SDK Team
Andrey K <kotkov...@gmail.com>: May 29 12:27AM -0700

Hi Nicholas,
 
Thank you for the code example.
 
We aim to utilize Ad caching to enhance our users' app experience. By
displaying cached Ads immediately, we can prevent any UI disruptions that
occur when Ads are loaded in real-time. Based on my understanding, caching
AdViews is permitted.
 
According to this link
(https://groups.google.com/g/google-admob-ads-sdk/c/OAGAtvMJyXE/m/4q6bTdzMBwAJ), preloading
ads in 2023 (and I hope in 2024) is still fine.
 
I would be interested to know if you could provide us with any suggestions
on how to fix or prevent this crash using Ads caching.
On Tuesday, May 28, 2024 at 11:18:47 PM UTC+2 Mobile Ads SDK Forum Advisor
wrote:
 
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 05:40PM

Hi Andrey,
 
Give me some time to cross check this issue with the Jetpack team. I will let you know the results shortly.
This message is in relation to case "ref:!00D1U01174p.!5004Q02hOxjC:ref" (ADR-00162006)
 
Thanks,
 
Nicholas Ventimiglia
Mobile Ads SDK Team
suchat <suchatch...@gmail.com>: May 29 03:39AM +0700

ไม่เข้าใจเลย อัพโหลดไฟล์จากไหน??
 
ในวันที่ พ. 29 พ.ค. 2024 00:24 alex...@gmail.com <alex...@gmail.com>
เขียนว่า:
 
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 05:24PM

Hello Alex,
 
Thanks for the information.
 
Would you be able to reproduce the issue in our Banner example as well?
 
If you do, can you provide the following?
 
Steps to reproduce
Full stack trace
Screenshot(s) or recording(s) captured in memory profiler that show memory leak
 
If not, can you provide the following?
 
Your sample project
Steps to reproduce
Full stack trace
Screenshot(s) or recording(s) captured in memory profiler that show memory leak
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02qXhCo:ref" (ADR-00214696)
 
Thanks,
 
Joshua Hui
Mobile Ads SDK Team
IngJobs <tg...@teamblind.com>: May 28 11:42PM -0700

Hello,
 
We are currently experiencing the following crash in our app
 

 
*Fatal Exception: java.lang.NullPointerException*
*Attempt to invoke interface method 'void
com.google.android.gms.ads.internal.webview.j.e(java.lang.String,
java.util.Map)' on a null object reference*
 
 
*com.google.android.gms.ads.nonagon.ad.nativead.co.run
(:com.google.android.gms.policy_ads_fdr_dynamite@233012805@233012802057.555274289.555274289:10)*
*arrow_drop_down*
*android.os.Handler.dispatchMessage (Handler.java:99)*
*arrow_right*
*m.avi.a
(:com.google.android.gms.policy_ads_fdr_dynamite@233012805@233012802057.555274289.555274289:1)*
*com.google.android.gms.ads.internal.util.zzae.a
(com.google.android.gms:play-services-ads@@22.0.0:2)*
*m.avi.dispatchMessage
(:com.google.android.gms.policy_ads_fdr_dynamite@233012805@233012802057.555274289.555274289:1)*
*android.os.Looper.loopOnce (Looper.java:230)*
*arrow_drop_down*
*com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1103)*
 
We are using com.google.android.gms:play-services-ads:22.0.0.
We upgraded to this version in August 2023, but since May 15, 2024, the
occurrence of this crash has suddenly increased.
We are wondering if this issue is related to Google’s servers, if we need
to address it in our app, or if we need to upgrade the SDK version.
 
We would appreciate a prompt response.
 
Thank you.
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 01:07PM

Hi,
 
I have run our Google sample project with your mentioned (22.0.0) SDK Version in emulator and I don’t see any cashes for the app. Could you please attempt to run our Google sample project with latest SDK version (23.1.0) and confirm the results?
 
It's always recommended to keep the SDKs up to date. As of today the latest version is 23.1.0. Please refer to these Google Mobile SDK release notes.
 
If the issue still persists after updating the GMA SDK version, kindly provide us with the below information for further investigation privately:
 
Breakdown of device/OS versions affected
Frequency of crashes
Sample project replicating the issue along with affected app ID and ad unit ID
 
If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, kindly provide requested information to us via reply to author option or using the steps below:
 
1. Navigate to
 
https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=5004Q00002tJ7TLQA0&entry.80707362=00236946
 
2. Fill out all fields, and attach your file(s).
 
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ7TL:ref" (ADR-00236946)
 
Thanks,
 
Mobile Ads SDK Team
"AYAPANA ARNOLD D." <arnolda...@gmail.com>: May 29 12:09AM -0700

TurboModule Registry.getEnforcing(...): 'RNGestureHandlerModule' could not
be found. Verify that a module by this name is registered in the native
binary. Bridgeless mode: false. TurboModule interop: false. Modules loaded:
("NativeModules":["PlatformConstants","Log Box",
"SourceCode","Timing","AppState","Blob Module","WebSo
cketModule","DevSettings","Dev Tools Settings Manager","Netw
orking","Appearance","DevLoadingView","HeadlessJsTaskSup
port","DeviceInfo","UIManager","ImageLoader","SoundManag
er","IntentAndroid","Device EventManager","NativeAnimatedM
odule","RNCSafeAreaContext","118nManager"],"TurboModules":
[],"NotFound":["NativePerformanceCxx","Native PerformanceOb
serverCxx","RedBox","Bug Reporting","Linking Manager","NativeR eactNative
FeatureFlagsCxx","RNGestureHandlerModule"]}
Mobile Ads SDK Forum Advisor <mobile...@forumsupport.google>: May 29 09:38AM

Hi Ayapana,
 
Thank you for contacting us.
 
Please note that we can only assist with technical queries/concerns related to the Mobile Ads SDK. If you are facing an issue with Google Mobile Ads SDK, kindly elaborate on the issue for further investigation.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ7TG:ref" (ADR-00236945)
 
Thanks,
 
Mobile Ads SDK Team
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...@googlegroups.com.

Mobile Ads SDK Forum Advisor

unread,
May 30, 2024, 8:57:08 AM5/30/24
to delapena...@gmail.com, google-adm...@googlegroups.com

Hi George,

Please be informed that our support channel can only best assist you with regards to Google Mobile Ads SDK implementation and technical issues. Having said that, would you be able to confirm if you have any issues with the SDK? If so, kindly elaborate it here and give full context of your concern so we can guide you accordingly.

 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tJ6SB:ref" (ADR-00236713)

Thanks,
 
Google Logo Mobile Ads SDK Team


Reply all
Reply to author
Forward
0 new messages