Performance issues and fatal crashes caused by WMS layer

[UsamaAndroid]

Verification of void com.google.android.gms.common.api.internal.zacp.() took 123.523ms or Skipped 161 frames! The application may be doing too much work on its main thread. before app crashes andoid studio shows one of these but mostly it gives me skipped frames error in run window of android studio and finally app crashes(closed).

[JaffaKetchup]

Hi @UsamaAndroid,
Can I ask why you closed this? Did you resolve your issue?
Thanks.

[UsamaAndroid]

Hi @UsamaAndroid, Can I ask why you closed this? Did you resolve your issue? Thanks.

sorry @JaffaKetchup i accidently closed it i just posted new one and i am going to delete this ok Luka bro?

[JaffaKetchup]

No problem. I just reopened this one though for you.

[UsamaAndroid]

@JaffaKetchup thanks bro you are great. What about the issue can it be resolved ?

[JaffaKetchup]

Yeah no problem.

At the moment, I can't really help too much. This seems to be one of many fatal performance issues, which do need to be fixed urgently. Unfortunately, I am not 100% familiar with the code (for reasons explained in a Discussion), meaning that I will need to do some learning to help people better.
I am quite busy right now, as my library is coming up to release. But hopefully after that I can spend a lot more of my time on here helping users.
I have been thinking for a while that flutter_map may need rewriting to a certain extent, but that conversation is out of scope for this issue.

In the meantime, it might help if you can:

• Give information about the device that this library is crashing on
• Try progressively manually going back through commits (using dependencies from Git), to see where this issue was introduced
• Attach any screen recordings

Thanks for your report, and sorry I'm unable to assist very well at the moment!