Using SupportMapFragment.newInstance(GoogleMapOptions) crashes the app [132314160]

Obsolete

Bug

Status Update

No update yet.

Description

ta...@appcorner.eu

created issue #1

May 9, 2019 11:21AM

When using SupportMapFragment.newInstance(options) to create a map fragment, the app crashes with the following stack trace:

E/AndroidRuntime: FATAL EXCEPTION: main
Process: eu.appcorner.mapsv3.mapoptionscrash, PID: 23773
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.os.Bundle.putParcelable(java.lang.String, android.os.Parcelable)' on a null object reference
at com.google.android.libraries.maps.SupportMapFragment$zza.onCreate(SupportMapFragment.java:10)
at com.google.android.gms.dynamic.zac.zaa(Unknown Source:3)
at com.google.android.gms.dynamic.zaa.onDelegateCreated(Unknown Source:4)
at com.google.android.libraries.maps.SupportMapFragment$zzb.zza(SupportMapFragment.java:15)
at com.google.android.libraries.maps.SupportMapFragment$zzb.createDelegate(SupportMapFragment.java:6)
at com.google.android.gms.dynamic.DeferredLifecycleHelper.zaa(Unknown Source:18)
at com.google.android.gms.dynamic.DeferredLifecycleHelper.onCreate(Unknown Source:22)
at com.google.android.libraries.maps.SupportMapFragment.onCreate(SupportMapFragment.java:32)
at androidx.fragment.app.Fragment.performCreate(Fragment.java:2414)
at androidx.fragment.app.FragmentManagerImpl.moveToState(FragmentManager.java:1418)
at androidx.fragment.app.FragmentTransition.addToFirstInLastOut(FragmentTransition.java:1195)
at androidx.fragment.app.FragmentTransition.calculateFragments(FragmentTransition.java:1078)
at androidx.fragment.app.FragmentTransition.startTransitions(FragmentTransition.java:117)
at androidx.fragment.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2408)
at androidx.fragment.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2366)
at androidx.fragment.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2273)
at androidx.fragment.app.FragmentManagerImpl.dispatchStateChange(FragmentManager.java:3273)
at androidx.fragment.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java:3229)
at androidx.fragment.app.FragmentController.dispatchActivityCreated(FragmentController.java:201)
at androidx.fragment.app.FragmentActivity.onStart(FragmentActivity.java:620)
at androidx.appcompat.app.AppCompatActivity.onStart(AppCompatActivity.java:178)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1391)
at android.app.Activity.performStart(Activity.java:7165)
at android.app.ActivityThread.handleStartActivity(ActivityThread.java:2975)
at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:180)
at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:165)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:142)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1816)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6718)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

Using the zero-argument version of SupportMapFragment.newInstance works fine.

Device: Pixel 3 XL, Android 9
Maps SDK Version: 3.0.0-beta (worked fine with v2)
Android SDK Version: 28

Sample code:

https://github.com/AppCornerHQ/maps-sdk-v3-mapoptions-crash

Comments

sh...@google.com <sh...@google.com> #2May 17, 2019 04:21AM

Status: Won't Fix (Infeasible)

Thanks for the post. Please note that the public issue tracker is not supposed to be used for issues like this one. It is aimed to report API bugs and feature requests and does not have guaranteed response times.

This seems to be an error with the syntax, kindly try to change "savedInstanceState == null" into "savedInstanceState != null". For future implementation issues, kindly redirect your query to Stackoverflow and add the following tag: [google-maps], [google-maps-android-api-2] for better visibility for our Google Advocates who can help you with your implementation issues.

ta...@appcorner.eu <ta...@appcorner.eu> #3May 17, 2019 02:20PM

The crash occurs inside your library, please review the stack trace again and consider reopening the ticket. The line you are referring to - although might seem similar - is in fact correct and entirely unrelated to the crash.

bo...@gmail.com <bo...@gmail.com> #4May 17, 2019 02:40PM

I'm seeing the same stack trace for the the same reason: use of SupportMapFragment.newInstance(options). I agree with the poster that this is a bug in Maps SDK Beta.

Message last modified on May 17, 2019 02:40PM

jh...@google.com <jh...@google.com> May 17, 2019 09:00PM

Status: Assigned (reopened)

br...@basebeta.com <br...@basebeta.com> #5Nov 3, 2019 08:35PM

This is exactly why I am trying out Mapbox. If a director at google is reading this, this behavior is common across google's repositories whether they be for iOS, web, or android. You guys aggressively close tickets and suggest stackoverflow when users report valid issues. You should be paying these guys for taking the time to report reproduction steps and not immediately switching to a competitor.

Oh, and I am seeing this issue as well.

ra...@google.com <ra...@google.com> Jan 15, 2020 05:46AM

Status: Won't Fix (Obsolete)

bo...@gmail.com <bo...@gmail.com> #6Apr 5, 2020 06:27PM

Could the assignee please elaborate what the status of Obsolete means? Has any attempt been made to reproduce or investigate this problem?

Eleven months ago I converted working code to use the Maps 3.0.0 Beta version and got this crash. I just tried again with the latest Maps and play-services libs and am still getting the crash. Just to be clear: I have an app that runs error free with the Google Play services version of Maps, I migrate to Maps 3.0.0 Beta using the instructions in the docs, the app crashes with the call stack reported here. If, for debug, I change my code to call SupportMapFragment.newInstance() instead of SupportMapFragment.newInstance(options), the crash does not occur.