godofredoc

Let's try with `9c72f5a7e62e63c199739267f3feeee0559caf11`

3d2504951c0bc794f186da29d35eabec0343e62d was included in a release candidate branch which caused the binaries to be signed. My first thought was something related to signing but if 9c72f5a7e62e63c199739267f3feeee0559caf11 is failing in the...

@borjandev are these files in your app tree: `entitlements.txt` and `without_entitlements.txt`? If they are can you please delete them and try to sign again?

Let me replicate the build locally. Seems like a symlink may be the culprit. Will use https://github.com/flutter/flutter/commit/3d2504951c0bc794f186da29d35eabec0343e62d for the replication and engine hash `689eb6ee904772cf1ffa458ac7fa16b903215c8f`

@borjandev can you please give it another try using https://github.com/flutter/flutter/commit/3d2504951c0bc794f186da29d35eabec0343e62d and deleting and regenerating the app?

That's correct, it will be great if you can re-rerun with `3d2504951c0bc794f186da29d35eabec0343e62d`. I just re-generated the debug, profile and release artifacts for that commit and re-upload them to GCS.

This is great news, if that works we'll send a fix on Monday and cherry pick it to Beta. For context the issue is caused by the new signing metadata...

No yet, I applied the changes manually to that specific commit to triage the problem and test the potential fix. We'll prepare the fix on Monday morning to fix the...

Is the setup of the test removing the old version of the application? or is there a crash when the test is trying to remove the application?

Should we try to uninstall the app before installing it? Here is a potential scenario: * Another test that is not doing proper cleanup is leaving the application installed, then...