#Essential Kit V2 - Sharing - Crash on Device with API 35 (and 34?) - Unity 2020.3.48f1

1 messages · Page 1 of 1 (latest)

earnest zenith
#

Hi there!

First off: amazing asset, congrats! I look forward to implementing more of the services.

But also: Help! 😄 I'm on the verge of releasing my indie mobile word puzzle game and on a whim (but with good reason) I decided to add an option to share text messages to brag about progress or ask for help. I ultimately chose your asset over something only offering just that service because of the volume of cool stuff you have. Currently, I'm ONLY using the sharing service.

Completely unrelated, I wanted to test the behaviour on a fold phone emulator to handle the aspect ratio change but noticed the game is crashing on an emulator with API 35 at startup with the following log One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts.

A lot of googling brought up the change made in API 34 where something to do with receiver_exported is now a requirement. Your name also came up on one of the threads I stumbled upon. 😄 So I checked the previous build (just before adding Essential Kit) and it runs on the API 35 emulator device without crashing.

Do you have any thoughts on things I could try? I can't upgrade my Unity version without having to rebuild my physics system so I'd like to avoid that (if possible!).

earnest zenith
#

Ok. New information. It doesn't crash consistently. Could this just be emulator issues? I've added a whole bunch on them thinking I'd be able pinpoint which versions weren't playing nicely with which builds but it honestly seems to be a bit random. And I've just successfully opened the previous build that crashed on the pixel fold running API 35.

This is my first time testing out the emulators so perhaps it's all just newbie inexperience.

If you have any insight on what might be going on, I'm all ears, but the fact that the same build is now running, leads me to believe it's not a problem with the Sharing service at all. Plus I've hunted up and done for anything that might have been registering a receiver dynamically and hit a blank.

Thanks again for an awesome asset!!

white temple
#

Please share the complete crash log to have a look.

#

I scheduled for api 35 support in V3 but V2 should work fine too as there are not much major changes related to the plugin.

earnest zenith
white temple
#

sounds like an unity issue and not specific to the plugin.

#

What unity version you are on?

earnest zenith
#

Unity 2020.3.48f1 - but I can't upgrade my Unity version without having to rebuild my string physics system so I'd like to avoid that (if possible!).

white temple
#

If you are targeting API 34, I don't see any other alternative. You can confirm this by just making a build with target api as 33 and it won't crash.