Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xamarin Assertion failure 'align > 0' #934

Closed
borrrden opened this issue Dec 5, 2017 · 4 comments
Closed

Xamarin Assertion failure 'align > 0' #934

borrrden opened this issue Dec 5, 2017 · 4 comments

Comments

@borrrden
Copy link
Member

borrrden commented Dec 5, 2017

Upstream bug

Not much we can do about this, but keeping it here in case users start hitting it. The solution is to downgrade to Xamarin Android 8.0 / iOS 11.3 or below. The upstream bug is marked "fixed" because it was fixed in the mono repo, but those changes didn't propagate into the Xamarin release (They are still using 2017/06 mono)

@djpongh djpongh added this to the 2.0.0 milestone Dec 8, 2017
@djpongh djpongh added the backlog label Dec 8, 2017
borrrden added a commit that referenced this issue Dec 11, 2017
…ential workaround for #934 [Xamarin Assertion failure 'align > 0'])
@borrrden borrrden modified the milestones: 2.0.0, 2.0 DB 21 Dec 12, 2017
@borrrden borrrden added bug and removed known-issue labels Dec 12, 2017
@borrrden
Copy link
Member Author

Testing shows that this causes the issue to go away. DB021 will include the workaround.

@ghost
Copy link

ghost commented Dec 20, 2017

Hi,

Before I open a new issue, I'm still experiencing the Xamarin Assertion failure 'align > 0' with 2.0 DB 21.

To make sure I understand, Is my only choice to downgrade my Xamarin.Android or is the workaround for the default() for unsafe struct supposed to fix the issue??

@borrrden
Copy link
Member Author

Downgrading to the appropriate version will work. I didn't see the issue anymore with the fix I included in db021, but it wasn't guaranteed in all cases I guess. The downstream fix should be coming in 15.6

@ghost
Copy link

ghost commented Dec 20, 2017

I fixed the problem, I had to uninstall my app and reinstall it for it to work... something was probably left lingering.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants