Interstitial Admob ads: “IllegalStateException: Only fullscreen activities can request orientation”

4,186 views
Skip to first unread message

Ishroid

unread,
Nov 30, 2017, 3:37:08 AM11/30/17
to Google Mobile Ads SDK Developers
Because of this commit i am not able to use full screen ads on device running 27 ( O ).
supportLibraryVersion = '27.0.1'
playServicesVersion = '11.6.0'


E/UncaughtException: java.lang.RuntimeException: Unable to start activity ComponentInfo{(my.package)/com.google.android.gms.ads.AdActivity}: java.lang.IllegalStateException: Only fullscreen activities can request orientation
                                                                 at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2946)
                                                                 at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3046)
                                                                 at android.app.ActivityThread.-wrap11(Unknown Source:0)
                                                                 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1688)
                                                                 at android.os.Handler.dispatchMessage(Handler.java:105)
                                                                 at android.os.Looper.loop(Looper.java:164)
                                                                 at android.app.ActivityThread.main(ActivityThread.java:6809)
                                                                 at java.lang.reflect.Method.invoke(Native Method)
                                                                 at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
                                                                 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
                                                              Caused by: java.lang.IllegalStateException: Only fullscreen activities can request orientation
                                                                 at android.os.Parcel.readException(Parcel.java:1950)
                                                                 at android.os.Parcel.readException(Parcel.java:1888)
                                                                 at android.app.IActivityManager$Stub$Proxy.setRequestedOrientation(IActivityManager.java:5918)
                                                                 at android.app.Activity.setRequestedOrientation(Activity.java:5762)
                                                                 at com.google.android.gms.ads.internal.overlay.d.a(:com.google.android.gms.DynamiteModulesA@11746440:182)
                                                                 at com.google.android.gms.ads.internal.overlay.d.b(:com.google.android.gms.DynamiteModulesA@11746440:216)
                                                                 at com.google.android.gms.ads.internal.overlay.d.a(:com.google.android.gms.DynamiteModulesA@11746440:76)
                                                                 at com.google.android.gms.ads.internal.overlay.client.c.onTransact(:com.google.android.gms.DynamiteModulesA@11746440:8)
                                                                 at android.os.Binder.transact(Binder.java:622)
                                                                 at com.google.android.gms.internal.zzed.zzb(Unknown Source:7)
                                                                 at com.google.android.gms.internal.zzwl.onCreate(Unknown Source:8)
                                                                 at com.google.android.gms.ads.AdActivity.onCreate(Unknown Source:29)
                                                                 at android.app.Activity.performCreate(Activity.java:6998)
                                                                 at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1230)
                                                                 at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2899)
                                                                 at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3046) 
                                                                 at android.app.ActivityThread.-wrap11(Unknown Source:0) 
                                                                 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1688) 
                                                                 at android.os.Handler.dispatchMessage(Handler.java:105) 
                                                                 at android.os.Looper.loop(Looper.java:164) 
                                                                 at android.app.ActivityThread.main(ActivityThread.java:6809) 
                                                                 at java.lang.reflect.Method.invoke(Native Method) 
                                                                 at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240) 
                                                                 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767) 

Deepika Uragayala- MobileAds SDK team

unread,
Nov 30, 2017, 2:34:10 PM11/30/17
to Google Mobile Ads SDK Developers
Hi there,

Thank you for reporting this to us. This is a known issue and our team has fixed this and it is expected to be out with our future SDK releases. While we do not provide any ETA for any fix, we would suggest that you keep an eye out on our release history page for all updates.

Regards,
Deepika Uragayala
Mobile Ads SDK Team

Nguyễn Triết Khang

unread,
Dec 16, 2017, 12:53:09 AM12/16/17
to Google Mobile Ads SDK Developers
Please hurry up, we're waiting for this bug fix to roll out, all android O users keep crashing.

Markus Wiederkehr

unread,
Dec 20, 2017, 6:39:08 AM12/20/17
to Google Mobile Ads SDK Developers
Has this been fixed in 11.8.0?

Deepika Uragayala- MobileAds SDK team

unread,
Dec 20, 2017, 3:08:56 PM12/20/17
to Google Mobile Ads SDK Developers
Hi there,

Thanks for the follow-up. The issue has been fixed and it is included in the latest SDK release

Regards,
Deepika Uragayala
Mobile Ads SDK Team



Szymon Klimaszewski

unread,
Dec 23, 2017, 6:04:31 PM12/23/17
to Google Mobile Ads SDK Developers
No, it's not. Still crashing on 11.8.0

Nguyễn Triết Khang

unread,
Dec 23, 2017, 9:12:35 PM12/23/17
to Google Mobile Ads SDK Developers
Version 11.8.0 still crash:
Unable to start activity ComponentInfo{com.myapp/com.google.android.gms.ads.AdActivity}: java.lang.IllegalStateException: Only fullscreen activities can request orientation

Especially, OnePlus devices caused 100% of crash.

Rajubhai Rathod

unread,
Dec 24, 2017, 4:31:23 AM12/24/17
to Google Mobile Ads SDK Developers
Hi !
Its still crashing with one plus 3 device android 8.0 and
com.google.android.gms:play-services-ads:11.8.0
Thanks

ltp.l...@gmail.com

unread,
Dec 26, 2017, 1:36:26 AM12/26/17
to Google Mobile Ads SDK Developers
Fatal Exception: java.lang.RuntimeException
Unable to start activity ComponentInfo{com.ltp.pro.fakelocation/com.google.android.gms.ads.AdActivity}: java.lang.IllegalStateException: Only fullscreen activities can request orientation
firebase version 11.8.0
ONEPLUS A5000
Android 8.0
100% CRASH
Please fix it

Deepika Uragayala- MobileAds SDK team

unread,
Dec 27, 2017, 3:02:56 PM12/27/17
to Google Mobile Ads SDK Developers
Hi guys,

Thank you for reporting this back to us. We will pass this information to the rest of the team for further investigation. I'll update this thread if I have any updates to share.

Regards,
Deepika Uragayala
Mobile Ads SDK Team


PA

unread,
Jan 13, 2018, 11:01:14 PM1/13/18
to Google Mobile Ads SDK Developers
Hi Deepika,
This issue is still happening with Admob SDK 11.8.0 on Android 8.x and is affecting our business. Any updates on fix in Admob?

Thanks.

Joshua Lagonera (Mobile Ads SDK Team)

unread,
Jan 14, 2018, 11:24:25 PM1/14/18
to Google Mobile Ads SDK Developers
Hi there,

I saw that you already posted your concern on this thread. For consistency, I would suggest that we continue our discussion from there.

Regards,
Joshua Lagonera
Mobile Ads SDK Team
Message has been deleted

Omar Mahmoud

unread,
Feb 7, 2018, 8:53:47 AM2/7/18
to Google Mobile Ads SDK Developers
try to add this in your manifest  
<activity
android:name="com.google.android.gms.ads.AdActivity"
android:theme="@android:style/Theme.NoTitleBar.Fullscreen"
tools:replace="android:theme"
/>

Joshua Lagonera (Mobile Ads SDK Team)

unread,
Mar 1, 2018, 1:23:08 AM3/1/18
to Google Mobile Ads SDK Developers
Hi All,

I would just like to inform you that a fix has been made for this crash issue. However, we are not able to comment on when it will be released. Kindly monitor our Release Notes for Android for any release updates for the Android Mobile Ads SDK.

Pavel Repkin

unread,
Mar 2, 2018, 9:43:34 AM3/2/18
to Google Mobile Ads SDK Developers
This solution fixed the crash for us.

Ameer Hamza

unread,
Oct 3, 2018, 8:49:23 AM10/3/18
to Google Mobile Ads SDK Developers

Still not fixed.


On Thursday, November 30, 2017 at 1:37:08 PM UTC+5, Ishroid wrote:
Because of this commit i am not able to use full screen ads on device running 27 ( O ).
supportLibraryVersion = '27.0.1'
playServicesVersion = '11.6.0'

here my top level gradle look like
classpath 'com.google.gms:google-services:4.1.0'

And my App level gradle


compileSdkVersion 28
//noinspection GradleCompatible
implementation 'com.google.firebase:firebase-ads:15.0.1'
implementation 'com.google.android.ads.consent:consent-library:1.0.6'
implementation 'com.google.firebase:firebase-core:16.0.3'

mobileadssdk-a...@google.com

unread,
Oct 3, 2018, 5:38:21 PM10/3/18
to Ameer Hamza, Google Mobile Ads SDK Developers
Hi there,

Thanks for reporting this to us. Can you provide us a sample project or your app link that reproduces the issue? Are you able to reproduce the issue with our sample apps? Please make sure that you are on the latest version of the SDK and send the requested details and we will take a look.

Regards,
Deepika Uragayala
Mobile Ads SDK Team
~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

--

---
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/afe7c60c-dd8c-4a71-ba60-2d0a5bcc693f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Greg Kochaniak

unread,
Nov 13, 2018, 1:55:29 PM11/13/18
to Google Mobile Ads SDK Developers
I am very disappointed with the quality of Mobile Ads SDK - this bug creeps in over and over. The app is compiled to targetSdk 28, and the crashes reported are only on Android 8.0.0. It's really frustrating, I'm reading at the start of this thread that the "team is working to solve this" posted over a year ago, and we still suffer this. Here are a few stack traces:

Operating System

8.0.0
OS Version

Portrait
UI Orientation
FIG-LX3
Device

Portrait
Orientation

On
Proximity

Caused by java.lang.IllegalStateException: Only fullscreen activities can request orientation
       at android.os.Parcel.readException(Parcel.java:1954)
       at android.os.Parcel.readException(Parcel.java:1892)
       at android.app.IActivityManager$Stub$Proxy.setRequestedOrientation(IActivityManager.java:5683)
       at android.app.Activity.setRequestedOrientation(Activity.java:6121)
       at com.google.android.gms.ads.internal.overlay.zzd.close(:com.google.android.gms.policy_ads_fdr_dynamite@8010@8010.217755688.217755688:13)
       at com.google.android.gms.ads.internal.overlay.zzd.zznh(:com.google.android.gms.policy_ads_fdr_dynamite@8010@8010.217755688.217755688:19)
       at com.google.android.gms.ads.internal.overlay.zzd.close(:com.google.android.gms.policy_ads_fdr_dynamite@8010@8010.217755688.217755688:36)
       at com.google.android.gms.ads.internal.overlay.client.c.a(:com.google.android.gms.policy_ads_fdr_dynamite@8010@8010.217755688.217755688:2)
       at os.onTransact(:com.google.android.gms.policy_ads_fdr_dynamite@8010@8010.217755688.217755688:5)
       at android.os.Binder.transact(Binder.java:605)
       at com.google.android.gms.internal.ads.zzej.transactAndReadExceptionReturnVoid(Unknown Source:7)
       at com.google.android.gms.internal.ads.zzaar.onCreate(Unknown Source:8)
       at com.google.android.gms.ads.AdActivity.onCreate(Unknown Source:29)
       at android.app.Activity.performCreate(Activity.java:7372)
       at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1218)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3147)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3302)
       at android.app.ActivityThread.-wrap12(Unknown Source)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1891)
       at android.os.Handler.dispatchMessage(Handler.java:108)
       at android.os.Looper.loop(Looper.java:166)
       at android.app.ActivityThread.main(ActivityThread.java:7425)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921)


Device

SM-A720F
Device

Portrait
Orientation

On
Proximity
Operating System

8.0.0
OS Version

Portrait
UI Orientation

No
Rooted





Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.hyperionics.avar/com.google.android.gms.ads.AdActivity}: java.lang.IllegalStateException: Only fullscreen activities can request orientation
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2957)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3032)
       at android.app.ActivityThread.-wrap11(Unknown Source)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)

       at android.os.Handler.dispatchMessage(Handler.java:105)
       at android.os.Looper.loop(Looper.java:164)
       at android.app.ActivityThread.main(ActivityThread.java:6944)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)

etc. etc. etc. - dozens and dozens of these and similar.

Greg

On Thursday, November 30, 2017 at 3:37:08 AM UTC-5, Ishroid wrote:

mobileadssdk-a...@google.com

unread,
Nov 13, 2018, 3:23:33 PM11/13/18
to Greg Kochaniak, Google Mobile Ads SDK Developers
Hi Greg,

Can you please help us with more information to investigate this issue? Our team would like to know if anyone is able to reproduce the issue locally and if they are able to, we would like to see the charles logs and steps to reproduce the issue on our end. 

Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
--

---
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.

mobileadssdk-a...@google.com

unread,
Nov 14, 2018, 2:48:23 PM11/14/18
to Greg Kochaniak, google-adm...@googlegroups.com
Hi Greg,

Thanks for sharing more information. I'll share this with the rest of the team and will update you if there is any new information to share.

Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 11/13/18 17:17:44 gr...@kochaniak.com wrote:
Hello Deepika,
I don't have a device where this bug happens, actually don't have any real device with Android 8, only emulators. Tried to reproduce it under an emulator, but could not. Also no user has contacted me directly about this issue, I only see dozens of crashes on Fabric Crashlytics.I'm not sure if you have seen my latest email to Matthew, so I'm pasting a fragment about a work-around that I found on StackOverflow, that fixes the issue for me (no more of these crashes reported on Crashlytics after implementing and releasing this workaround). Please read the quoted StackOverflow article too, it may give you additional hints on where to look for the root of the problem.

For the most common crash "IllegalStateException: Only fullscreen activities can request orientation" - they were happening mostly on Android 8, AdMob ads services ver. 17.1.0, Android compileSdkVersion and target SDK version 28. I found a work-around for them on StackOverflow. Here is what I did:

In AndroidManifest.xml declared:
<!--
Supposed workaround for AdMob SDK crash
IllegalStateException: Only fullscreen activities can request orientation
 -->
<activity
android:name="com.google.android.gms.ads.AdActivity"
android:theme="@style/TranslucentTheme"
    tools:replace="android:theme"
/>


Plus in values/styles.xml:
<!--
Supposed workaround for AdMob SDK crash
IllegalStateException: Only fullscreen activities can request orientation
 -->
<style name="TranslucentTheme" parent="Theme.AppCompat.NoActionBar">
<item name="android:windowFullscreen">true</item>
<item name="android:windowContentOverlay">@null</item>
<item name="android:windowBackground">@android:color/transparent</item>
<item name="android:colorBackgroundCacheHint">@null</item>
<item name="android:windowAnimationStyle">@android:style/Animation</item>
</style>
So far this workaround works fine, did not see these crashes anymore. It should be still fixed or work-around implemented directly in AdMob SDK to avoid problems for other and future users.

Greg

Greg Kochaniak

unread,
Nov 15, 2018, 3:00:02 PM11/15/18
to mobileadssdk-a...@google.com, google-adm...@googlegroups.com
Hello Deepika,
I don't have a device where this bug happens, actually don't have any real device with Android 8, only emulators. Tried to reproduce it under an emulator, but could not. Also no user has contacted me directly about this issue, I only see dozens of crashes on Fabric Crashlytics.I'm not sure if you have seen my latest email to Matthew, so I'm pasting a fragment about a work-around that I found on StackOverflow, that fixes the issue for me (no more of these crashes reported on Crashlytics after implementing and releasing this workaround). Please read the quoted StackOverflow article too, it may give you additional hints on where to look for the root of the problem.

For the most common crash "IllegalStateException: Only fullscreen activities can request orientation" - they were happening mostly on Android 8, AdMob ads services ver. 17.1.0, Android compileSdkVersion and target SDK version 28. I found a work-around for them on StackOverflow. Here is what I did:

In AndroidManifest.xml declared:
<!--
Supposed workaround for AdMob SDK crash
IllegalStateException: Only fullscreen activities can request orientation
 -->
<activity
android:name="com.google.android.gms.ads.AdActivity"
android:theme="@style/TranslucentTheme"
tools:replace="android:theme"
/>


Plus in values/styles.xml:
<!--
Supposed workaround for AdMob SDK crash
IllegalStateException: Only fullscreen activities can request orientation
 -->
<style name="TranslucentTheme" parent="Theme.AppCompat.NoActionBar">
<item name="android:windowFullscreen">true</item>
<item name="android:windowContentOverlay">@null</item>
<item name="android:windowBackground">@android:color/transparent</item>
<item name="android:colorBackgroundCacheHint">@null</item>
<item name="android:windowAnimationStyle">@android:style/Animation</item>
</style>
So far this workaround works fine, did not see these crashes anymore. It should be still fixed or work-around implemented directly in AdMob SDK to avoid problems for other and future users.

Greg

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To post to this group, send email to google-adm...@googlegroups.com.

Yan MESS

unread,
Nov 16, 2018, 12:50:09 PM11/16/18
to Google Mobile Ads SDK Developers
Hi guys,

Can you please confirm if we can remove these parts in AndroidManifest? I didn't find them in the new implementation of Admob SDK:
<activity
android:name="com.google.android.gms.ads.AdActivity"
android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize"
android:theme="@android:style/Theme.Translucent" />

<meta-data
android:name="com.google.android.gms.version"
android:value="@integer/google_play_services_version" />

I suspect the first part for being responsible on the reported bug that I also had where it says: “IllegalStateException: Only fullscreen activities can request orientation”.
Thanks,
Yan

mobileadssdk-a...@google.com

unread,
Nov 16, 2018, 7:49:34 PM11/16/18
to Yan MESS, Google Mobile Ads SDK Developers
Hello Yan, 

These are specific to your implementation. For example, if you're using any of the Mediation networks it is required that you specify these in the Android Manifest file. You can take a look at our sample apps as a reference. You may also refer to our mediation guide which might be helpful too. If you're having any issues implementing this, please let me know I will be happy to assist you. 

Thanks,
Bharani Cherukuri
Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Régis

unread,
Dec 4, 2018, 12:46:06 PM12/4/18
to google-adm...@googlegroups.com
This bug is still present on the last release play-services-ads:17.1.1 of the AdMob SDK. So, more than 1 year (perhaps 2 ?) that this bug exists...

When will it be solved ?

Thanks.

mobileadssdk-a...@google.com

unread,
Dec 4, 2018, 4:50:32 PM12/4/18
to Régis, Google Mobile Ads SDK Developers
Hello, 

The fix for this has been released and it relies on a JavaScript change. Our team was able to take a look at the logs shared and we suspect that some devices did not pick up this fix. How does the current number of crashes compare to the number of crashes a month ago?

Thanks,
Bharani Cherukuri
Mobile Ads SDK Team

Bao Le Duc

unread,
Jan 4, 2019, 6:50:43 AM1/4/19
to Google Mobile Ads SDK Developers

We are using com.google.android.gms:play-services-ads:17.1.0 
and still have that bug. Please checkout Crashlytics report

Yan MESS

unread,
Jan 4, 2019, 10:36:32 AM1/4/19
to Bao Le Duc, Google Mobile Ads SDK Developers
Hi there,
I confirm that this bug wasn't solved on the latest version 17.1.2. It happens only with Android 8.0 like most of the bugs from Google. Another annoying one is the famous "Context.startForegroundService() did not then call Service.startForeground" that happens also on Android 8.0 even if everything was done correctly. I think that Google should try to eliminate this buggy version of Android by releasing an update to 8.1 on all concerned devices.

Another bug even appeared now on Huawei P10 lite (HWWAS-H), Android 8.0:
java.lang.AssertionError:
at android.util.JsonReader.peek (JsonReader.java:363)
at android.util.JsonReader.expect (JsonReader.java:308)
at android.util.JsonReader.beginObject (JsonReader.java:293)
at com.google.android.gms.ads.nonagon.transaction.g.<init> (com.google.android.gms.dynamite_adsdynamite@14799051@14.7.99 (040408-223214910):8)
at com.google.android.gms.ads.nonagon.transaction.g.a (com.google.android.gms.dynamite_adsdynamite@14799051@14.7.99 (040408-223214910):1)
at com.google.android.gms.ads.nonagon.load.z.a (Unknown Source:3)
at com.google.android.gms.ads.internal.util.future.k.run (Unknown Source:3)
at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636)
at java.lang.Thread.run (Thread.java:784)

We are wating for a safe release that so that we can update our apps on other appstores that don't have automatic  SDK updates.

Greetings,
Yan

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/8zPchu8c0Ko/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.

To post to this group, send email to google-adm...@googlegroups.com.

mobileadssdk-a...@google.com

unread,
Jan 4, 2019, 10:42:01 AM1/4/19
to Yan MESS, Google Mobile Ads SDK Developers, Bao Le Duc
Hello, 

Thank you for the details. I have shared the crash reports with the team. I am checking this internally and will back to you on any further updates regarding this. 

Regards,
Bharani Cherukuri
Mobile Ads SDK Team

servic...@outlook.de

unread,
Jan 13, 2019, 7:30:49 AM1/13/19
to Google Mobile Ads SDK Developers
i have the same problem.

Messages from Crashlytics and pre-launch-testing in PlayStore:
FATAL EXCEPTION: ControllerMessenger
Process: xxx, PID: 10128
java.lang.RuntimeException: Unable to start activity ComponentInfo{xxx/com.google.android.gms.ads.AdActivity}: java.lang.IllegalStateException: Only fullscreen activities can request orientation
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2817)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2892)
	at android.app.ActivityThread.-wrap11(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1593)
	at android.os.Handler.dispatchMessage(Handler.java:105)

My dependencies:
compiledSdkVersion = 28
targetSdkVersion = 28
implementation 'com.google.firebase:firebase-ads:17.1.2'
implementation 'com.google.firebase:firebase-core:16.0.6'

Regards,
Duran

mobileadssdk-a...@google.com

unread,
Jan 14, 2019, 11:01:35 AM1/14/19
to servic...@outlook.de, Google Mobile Ads SDK Developers
Hello Duran, 

Thank you for reporting this. I have shared the logs with the team. I will update this thread on any further updates.

Regards,
Bharani Cherukuri
Mobile Ads SDK Team

Kiem Nguyen

unread,
Jan 14, 2019, 8:44:22 PM1/14/19
to Google Mobile Ads SDK Developers
This crash at setRequestedOrientation method  implementation for:

Not all devices 8.0 have this crash. Only devices 8.0 are not updated from the manufacturer. Hopefully version ads 17.1.3 will fix this crash. Thanks!

Vào 23:01:35 UTC+7 Thứ Hai, ngày 14 tháng 1 năm 2019, mobileadssdk-a...@google.com đã viết:

mobileadssdk-a...@google.com

unread,
Jan 15, 2019, 10:23:42 AM1/15/19
to Kiem Nguyen, Google Mobile Ads SDK Developers
Hello Nyugen, 

I'm sharing these details with the team. Please keep us posted on your findings. I will also update this thread on any further updates. 

Regards,
Bharani Cherukuri
Mobile Ads SDK Team

Yac Farm

unread,
Jan 16, 2019, 9:49:57 PM1/16/19
to Google Mobile Ads SDK Developers
I got this error too.

mobileadssdk...@google.com

unread,
Jan 17, 2019, 8:41:42 AM1/17/19
to Google Mobile Ads SDK Developers
Hello, 

This is known issue and our team is looking into this. I will update this thread on any further updates.

Thanks,
Bharani Cherukuri
Mobile Ads SDK Team

mobileadssdk...@google.com

unread,
Feb 14, 2019, 3:01:11 PM2/14/19
to Google Mobile Ads SDK Developers
Hello, 

Our team has fixed this issue. Could you please confirm if you're still seeing these crashes on the latest version of the SDK?

Thanks,
Bharani Cherukuri
Mobile Ads SDK Team

Yan MESS

unread,
Feb 15, 2019, 2:10:30 PM2/15/19
to mobileadssdk...@google.com, Google Mobile Ads SDK Developers
Hi,

How it can be fixed when there is no new release? The latest version (Firebase ads 17.1.2) was released on last December and we keep receiving these crashes and waiting for a new version that hopefully will fix it.

Greetings,
Yan

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/8zPchu8c0Ko/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
To post to this group, send email to google-adm...@googlegroups.com.

mobileadssdk...@google.com

unread,
Feb 15, 2019, 4:58:39 PM2/15/19
to Yan MESS, Google Mobile Ads SDK Developers
Hello Yan, 

This should be a JS fix and should be reduced over time. Could you please shared details (Crashlytics links) if you're seeing any increasing reports in the past one week? This will help us troubleshoot the issue.

Thanks,
Bharani Cherukuri
Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 02/15/19 14:09:59 millen...@gmail.com wrote:
Hi,

How it can be fixed when there is no new release? The latest version (Firebase ads 17.1.2) was released on last December and we keep receiving these crashes and waiting for a new version that hopefully will fix it.

Greetings,
Yan

On Thu, Feb 14, 2019, 21:01 mobileadssdk-forumadvisor via Google Mobile Ads SDK Developers <google-admob-ads-sdk@googlegroups.com wrote:
Hello, 

Our team has fixed this issue. Could you please confirm if you're still seeing these crashes on the latest version of the SDK?

Thanks,
Bharani Cherukuri
Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/8zPchu8c0Ko/unsubscribe.
To unsubscribe from this group and all its topics, 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.

mobileadssdk...@google.com

unread,
May 3, 2019, 11:48:43 AM5/3/19
to Yan MESS, Google Mobile Ads SDK Developers
Hello Yan,

Our team has developed a fix for this issue. Barring any setbacks, we expect the fix to go live in an upcoming SDK release.


Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 11/16/18 12:50:09 millen...@gmail.com wrote:

ling jerry

unread,
Jun 4, 2019, 2:30:33 PM6/4/19
to Google Mobile Ads SDK Developers
still crash on 17.2.1

在 2017年11月30日星期四 UTC+8下午4:37:08,Ishroid写道:
Because of this commit i am not able to use full screen ads on device running 27 ( O ).
supportLibraryVersion = '27.0.1'
playServicesVersion = '11.6.0'


E/UncaughtException: java.lang.RuntimeException: Unable to start activity ComponentInfo{(my.package)/com.google.android.gms.ads.AdActivity}: java.lang.IllegalStateException: Only fullscreen activities can request orientation
                                                                 at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2946)
                                                                 at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3046)
                                                                 at android.app.ActivityThread.-wrap11(Unknown Source:0)
                                                                 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1688)
                                                                 at android.os.Handler.dispatchMessage(Handler.java:105)
                                                                 at android.os.Looper.loop(Looper.java:164)
                                                                 at android.app.ActivityThread.main(ActivityThread.java:6809)
                                                                 at java.lang.reflect.Method.invoke(Native Method)
                                                                 at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
                                                                 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
                                                              Caused by: java.lang.IllegalStateException: Only fullscreen activities can request orientation
                                                                 at android.os.Parcel.readException(Parcel.java:1950)
                                                                 at android.os.Parcel.readException(Parcel.java:1888)
                                                                 at android.app.IActivityManager$Stub$Proxy.setRequestedOrientation(IActivityManager.java:5918)
                                                                 at android.app.Activity.setRequestedOrientation(Activity.java:5762)
                                                                 at com.google.android.gms.ads.internal.overlay.d.a(:com.google.android.gms.DynamiteModulesA@11746440:182)
                                                                 at com.google.android.gms.ads.internal.overlay.d.b(:com.google.android.gms.DynamiteModulesA@11746440:216)
                                                                 at com.google.android.gms.ads.internal.overlay.d.a(:com.google.android.gms.DynamiteModulesA@11746440:76)
                                                                 at com.google.android.gms.ads.internal.overlay.client.c.onTransact(:com.google.android.gms.DynamiteModulesA@11746440:8)
                                                                 at android.os.Binder.transact(Binder.java:622)
                                                                 at com.google.android.gms.internal.zzed.zzb(Unknown Source:7)
                                                                 at com.google.android.gms.internal.zzwl.onCreate(Unknown Source:8)
                                                                 at com.google.android.gms.ads.AdActivity.onCreate(Unknown Source:29)
                                                                 at android.app.Activity.performCreate(Activity.java:6998)
                                                                 at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1230)
                                                                 at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2899)

ling jerry

unread,
Jun 4, 2019, 2:34:44 PM6/4/19
to Google Mobile Ads SDK Developers
crash on samsung s8 ,api 26

在 2019年6月5日星期三 UTC+8上午2:30:33,ling jerry写道:

Mobile Ads SDK Forum Advisor Prod

unread,
Jun 5, 2019, 3:28:45 PM6/5/19
to wens...@gmail.com, google-adm...@googlegroups.com
Hello there,

Are you able to reproduce the crash locally with the latest version of the SDK? I will check our team about this and will get back to you with more information. 


Regards,
Deepika Uragayala
Mobile Ads SDK Team
 

ref:_00D1U1174p._5001UBlVVy:ref
Reply all
Reply to author
Forward
0 new messages