Android Build Crashes

  • updated
  • Fixed

Hi Freya!

Love Shapes, but keeps crashing while building for Android. Building for PC works great.

Tried on 2 different computers (PC), 2 different phones (Pixel 2 & 3) and with empty projects with only Shapes and a Line in the scene. 

I'm on 2019.4.9f1 LTS.

Can't provide you with errors since unity freezes and crashes right after this screenshot. I get: "Resolving used channels: Line 2D Transparent [CAP_ROUND] - Shapes/Line 2D Tra...: 25 of about 36)" for a split second before crashing.

Do you have any pointer at to why this is? 

Thank!

Reporting a bug? please specify Unity version:
2019.4.9f1
Reporting a bug? please specify Shapes version:
Latest as of 2020-09-10
Pinned replies
Freya Holmér
  • Answer
  • Fixed

Okay, I think we finally have an answer

  • Using Unity 2020? This shouldn't be an issue. If it still is an issue, even if you update, please open a new bug report here!
  • Using Unity 2019? This bug has recently been fixed in 2019.4 LTS, update your Unity!
    • Bug has been reported in 2019.4.8 and earlier
    • Users have reported it no longer happens in 2019.4.10 and later
  • Using Unity 2018? This bug persist until Unity has backported the fix! Hopefully sooner than later :)

Thanks everyone for trying to figure out this hecking nightmare of an issue! <3

Freya Holmér
  • Under Review

Still trying to hunt this down I'm afraid, having reported a bug to Unity :(
it's very weird and inconsistent. seems related to;
https://shapes.userecho.com/communities/1/topics/70-windows-build-error-with-webgl

Freya Holmér

I think I might have a lead on why this is happening. Shapes has special passes to make scene view selection work, and it looks like these are somehow interfering with the shader compiler process

so here's a workaround, that disables the scene view picking passes (so, doing this will make selection really annoying), but I believe this will make it compile

go to ShaderBuilder.cs
at line 70 and 71, you should see:

AppendPass( ShaderPassType.Picking, rp );
AppendPass( ShaderPassType.Selection, rp );
  1. remove or comment out those lines
  2. recompile scripts
  3. go to Shapes -> Advanced -> Regenerate Shaders & Materials
  4. go to Assets -> Reimport All

let me know if that makes it work again!

again - selection will be broken if you do this, but I'm currently talking to Unity to see if we can come up with a proper way to solve this!

Vamosia
Quote from Freya Holmér

I think I might have a lead on why this is happening. Shapes has special passes to make scene view selection work, and it looks like these are somehow interfering with the shader compiler process

so here's a workaround, that disables the scene view picking passes (so, doing this will make selection really annoying), but I believe this will make it compile

go to ShaderBuilder.cs
at line 70 and 71, you should see:

AppendPass( ShaderPassType.Picking, rp );
AppendPass( ShaderPassType.Selection, rp );
  1. remove or comment out those lines
  2. recompile scripts
  3. go to Shapes -> Advanced -> Regenerate Shaders & Materials
  4. go to Assets -> Reimport All

let me know if that makes it work again!

again - selection will be broken if you do this, but I'm currently talking to Unity to see if we can come up with a proper way to solve this!

Hey,

I'm also experiencing this issue on Unity 2019.4.0f1 (Win10). I've followed those steps but it doesn't manage to solve the issue for me :(.

Freya Holmér

sighs, okay :c I think we might be at Unity's mercy for this one - they're looking into it still

Michael Markman

Having the same issue, unity 2019.4.1! hopefully unity has an answer soon!

Cyan

Hey, I was using Unity 2019.4.0f1 on Win10 and had the same issue. After updating to 2019.4.11f1 it got magically solved. So I guess it was Unity's fault.

Updating is still not an ideal solution tho.

Freya Holmér

that's good to hear! can anyone else confirm if updating Unity fixes it?

Juanma Altamirano

Updating to 2019.4.10 and 2019.4.11 it got solved but trying with multiple 2018 LTS versions it still happening (including the latest version 2018.4.27)

Freya Holmér
  • Answer
  • Fixed

Okay, I think we finally have an answer

  • Using Unity 2020? This shouldn't be an issue. If it still is an issue, even if you update, please open a new bug report here!
  • Using Unity 2019? This bug has recently been fixed in 2019.4 LTS, update your Unity!
    • Bug has been reported in 2019.4.8 and earlier
    • Users have reported it no longer happens in 2019.4.10 and later
  • Using Unity 2018? This bug persist until Unity has backported the fix! Hopefully sooner than later :)

Thanks everyone for trying to figure out this hecking nightmare of an issue! <3