-
-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
SDK Parse 1.0.26 not usable - boolean expression must not be null #371
Comments
Hey
Can you provide more details around exactly where this error is being
triggered from? Is this on the health check when the app starts, or is this
a ParseObject, Live etc etc.
Thanks
…On Mon, 11 May 2020, 05:20 jeansebastienZ, ***@***.***> wrote:
Hi,
I'm making a new topic , as the old one get no answer and it still
problematic in order to use the last SDK .
Issue on Android
1. Create a new project
2. Basic initialisation :
Parse().initialize(
MyParse.applicationId,
MyParse.serverURL,
masterKey: masterKey,
clientKey: clientKey,
debug: true,
liveQueryUrl: liveQueryUrl,
autoSendSessionId: true);
3)[ERROR:flutter/lib/ui/ui_dart_state.cc(166)] Unhandled Exception:
Failed assertion: boolean expression must not be null
Where is the problem ? seem to refer to :
ParseHTTPClient.send
(package:parse_server_sdk/src/network/parse_http_client.dart:40:14)
Using parse_server_sdk: 1.0.21 with the same code , works perfectly .
However 1.0.21 is not usable if you need parse live query and subscription.
Can you try to dig and find out whats the problem please ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#371>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXQ5QHHJMRH2Z3SPSKTRQ54IVANCNFSM4M5SA6EQ>
.
|
Hello, It is on the health check when the app start :
|
Something sounds off here. I am pretty much the exact initialisation on app
start with no faults. What version of the lib are you using? Have you tried
deleting all build folders? I'm wondering if there's some old lib files
causing this issue.
…On Mon, 11 May 2020, 06:02 jeansebastienZ, ***@***.***> wrote:
Hello,
It is on the health check when the app start :
Parse().initialize(
MyParse.applicationId,
MyParse.serverURL,
masterKey: masterKey,
clientKey: clientKey,
debug: true,
liveQueryUrl: liveQueryUrl,
autoSendSessionId: true);
final ParseResponse response = await Parse().healthCheck();
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#371 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXXS6UZ6NCVCG63GMK3RQ6BFVANCNFSM4M5SA6EQ>
.
|
Can you also send across the logs showing the issue as well please.
…On Mon, 11 May 2020, 06:02 jeansebastienZ, ***@***.***> wrote:
Hello,
It is on the health check when the app start :
Parse().initialize(
MyParse.applicationId,
MyParse.serverURL,
masterKey: masterKey,
clientKey: clientKey,
debug: true,
liveQueryUrl: liveQueryUrl,
autoSendSessionId: true);
final ParseResponse response = await Parse().healthCheck();
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#371 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXXS6UZ6NCVCG63GMK3RQ6BFVANCNFSM4M5SA6EQ>
.
|
I post all my dependencies, if something is interfering, don't know : http: ^0.12.0+4 I would not find out the problem was a version related if #282 did not get the same problem . here the full logs showing the issue:
|
Very strange. I cannot replicate this issue. Can you try adding a persistant storage option?
Add this to the |
Hello Phill ,
Works , can you explain me why ? I trie on a new project and on my old , and for both with CoreStoreSembastImp.getInstance() it work . Thanks you for this , if you think you know why let me know then i'll close this one . |
It should work by default with just Sembast but it looks like a bug might
have been introduced.
We allowed users of the SDK to decide if they want to use mobile first
storage (SharedPrefs etc) or platform independent storage, such as Sembast.
It looks like if one isn't selected, no default is set. Although this isn't
the case on my own project.
…On Mon, 11 May 2020, 10:43 jeansebastienZ, ***@***.***> wrote:
Hello Phill ,
Parse().initialize(
MyParse.applicationId,
MyParse.serverURL,
masterKey: masterKey,
clientKey: clientKey,
debug: true,
liveQueryUrl: liveQueryUrl,
autoSendSessionId: true,
coreStore: await CoreStoreSembastImp.getInstance());
Works , can you explain me why ? I trie on a new project and on my old ,
and for both with CoreStoreSembastImp.getInstance() it work . Thanks you
for this , if you think you know why let me know then i'll close this one .
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#371 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXT7RWN66NM2IRECO6LRQ7CEFANCNFSM4M5SA6EQ>
.
|
Inside parse_core_data.dart a default CoreStore should be set.
|
Ok indeed i see , should be corrected for future users , basically , i didn't expect you to answer that fast , so thanks , you saved my day . Send paypal i'll make a small donation . Have a nice day . |
Your welcome.
If you would like to donate anything , please do so to the Parse groups
donations.
https://opencollective.com/parse-server
Thank you.
…On Mon, 11 May 2020, 10:53 jeansebastienZ, ***@***.***> wrote:
Ok indeed i see , should be corrected for future users , basically , i
didn't expect you to answer that fast , so thanks , you saved my day . Send
paypal i'll make a small donation . Have a nice day .
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#371 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXS6WEICTWMEWE4VQHTRQ7DKJANCNFSM4M5SA6EQ>
.
|
@phillwiggins |
Sounds like a logical solution?
…On Tue, 12 May 2020 at 10:39, Maximilian Fischer ***@***.***> wrote:
@phillwiggins <https://github.com/phillwiggins>
This is just an idea:
The password for the default CoreStore is masterKey. And masterKey should
be null in every published app. This might cause the assertion to fail.
I have not tested it, but it might be better to use the password
'flutter_sdk'. As this one is used inside the getInstance block as a
default.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#371 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4CPXSLT2YJWEUKQNIRMHTRREKM7ANCNFSM4M5SA6EQ>
.
--
Kind Regards
Phill Wiggins
Phill.Wiggins@Gmail.com
|
Unfortunately I have at the moment no time to give this a try. I will do so in several hours. |
In my case, when testing web app on chrome, it seems it shows different results as above. |
@phillwiggins I was not able to reproduce the issue using the |
It's a logical idea. It's strange that a crash is happening in this other issue. |
Hi,
I'm making a new topic , as the old one get no answer and it still problematic in order to use the last SDK .
Issue on Android
3)[ERROR:flutter/lib/ui/ui_dart_state.cc(166)] Unhandled Exception: Failed assertion: boolean expression must not be null
Where is the problem ? seem to refer to :
ParseHTTPClient.send (package:parse_server_sdk/src/network/parse_http_client.dart:40:14)
Using parse_server_sdk: 1.0.21 with the same code , works perfectly . However 1.0.21 is not usable if you need parse live query and subscription.
Can you try to dig and find out whats the problem please ?
The text was updated successfully, but these errors were encountered: