Skip to content

Failed Assertion: boolean expression must not be null; #282

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

Closed
iLolz opened this issue Oct 31, 2019 · 4 comments
Closed

Failed Assertion: boolean expression must not be null; #282

iLolz opened this issue Oct 31, 2019 · 4 comments

Comments

@iLolz
Copy link

iLolz commented Oct 31, 2019

I use the B4a in one app and the parse_server_sdk is allright, but in a new project when I try to get a class objects or upload any new object I received the error : "Failed assertion: boolean expression must not be null!", when I debug the error whas inside the parse_server_sdk, I redo all my Parse().initialize() and other lines of code trying concert that but nothing happen. I created a new project and tried to connect and the same error happens...

@phillwiggins
Copy link
Member

Hey

It's difficult to understand what the issue is without seeing a bit more code or a few more details. Do you have any code you can provide?

@iLolz
Copy link
Author

iLolz commented Nov 7, 2019

The problem was in the atualization, before he uses shared_preferences, in new versions the package changes, my function can't access the varible named "data" and nothing happens, in a error on downgrade parse_server_sdk version (i'm using the caracter "^" in my dependencies version and using this, Flutter get any version after the version i'm define, when I do that, the downgrade don't ocurred and i'm still use the parse_server_sdk version 1.0.24, when I change all happens again, because I put "^1.0.21", now I;m using "1.0.21",), It's something diferent in the implementation of the parse_server_sdk between versions 1.0.21 and 1.0.24, think thats ocurred througth change of "shared_preferences" to the new package... thank's for the atention!

@gorillatapstudio
Copy link

I have the same error msg with the latest version. All works for ios and android but for web app, it failed when i call the user.signup() function. The bug is confirmed with many repeated tests.

@RodrigoSMarques
Copy link
Contributor

We are closing issues that have been open for a long time without activity.
This will make it easier to organize things from now on.
If the problem persists, please open a new issue.
Thanks.

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

No branches or pull requests

4 participants