-
-
Notifications
You must be signed in to change notification settings - Fork 206
type '_InternalLinkedHashMap<String, dynamic>' is not a subtype of type 'ParseBase' #42
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
Comments
I'll check this out ASAP. Looks as though you Parse server URL might be
invalid but it should handle better than that.
…On Sun, Jan 20, 2019, 09:35 Vlad Rimsha ***@***.*** wrote:
Steps to reproduce
- open example from repository
- run
Description
It seems like on the request for health check, when response is returned
it crashes on the response.result = _handleSingleResult<T>(object, map);
line. I am not familiar enough with flutter and parse sdk to figure out the
problem on my own yet.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#42>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHgn3pbRXKdpA8Q1G5jDimcmI4Hi6qrGks5vFDhNgaJpZM4aJjcx>
.
|
Can you send a snippet of your code?
Even with the URL removed or invalid I have a good enough response. Is your
library up to date as 1.0.8?
Can't replicate.
…On Sun, Jan 20, 2019, 09:35 Vlad Rimsha ***@***.*** wrote:
Steps to reproduce
- open example from repository
- run
Description
It seems like on the request for health check, when response is returned
it crashes on the response.result = _handleSingleResult<T>(object, map);
line. I am not familiar enough with flutter and parse sdk to figure out the
problem on my own yet.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#42>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHgn3pbRXKdpA8Q1G5jDimcmI4Hi6qrGks5vFDhNgaJpZM4aJjcx>
.
|
Hey @phillwiggins that's for quick response.
I have this configuration inside
and I run my parse-server with this command: I just run from examples folder, so I guess my library version is master. |
Apologies, I meant the flutter_parse_sdk library being up to date.
It's strange as you are receiving a response from the server and that
should be handled but obviously is not matching what your server is sending
back.
Do you know how to debug the library... Make a breakpoint on the line
that's crashing. You should be able to get an idea of the response your
server is sending...
…On Sun, Jan 20, 2019, 15:34 Vlad Rimsha ***@***.*** wrote:
Hey @phillwiggins <https://github.com/phillwiggins> that's for quick
response.
My flutter version
Flutter 1.1.10-pre.78 • channel master • https://github.com/flutter/flutter.git
Framework • revision 105026cd68 (4 days ago) • 2019-01-16 08:13:00 -0800
Engine • revision 09e149e897
Tools • Dart 2.1.1 (build 2.1.1-dev.1.0 2195a70249)
I have this configuration inside ApplicationConstantsts
static const String keyAppName = "";
static const String keyParseApplicationId = "test";
static const String keyParseMasterKey = "key";
static const String keyParseServerUrl = "http://localhost:1337/parse";
}```
and I run my parse-server with this command: `parse-server --appId test --masterKey key --databaseURI mongodb://localhost/project-name`
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgn3k-VEQ0hh9KbyUkTbdVQVVes9hrzks5vFIyWgaJpZM4aJjcx>
.
|
Same thing here. I was using version 1.0.5 and It was working. Now it fails on the first request to the Parse server, in my case, healthCheck() as well. |
Okay, I will look at this ASAP. Strange error...
For this release just remove healthcheck. It's not actually necessary, but
will be fixed in the next day or so.
…On Mon, Jan 21, 2019, 01:39 Carlos Eugenio Torres ***@***.*** wrote:
Same thing here. It was working with the previous version of the lib. Now
it fails on the first request to the Parse server, in my case,
healthCheck() as well.
I cannot even start my app. Please fix it asap.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgn3hVcT78Z_IWLZEcIITSrHxxTCdpWks5vFRppgaJpZM4aJjcx>
.
|
Sorry, just for reference, can you breakpoint before the exception. In really curious as to the contents of the response but won't be in from of a computer until this afternoon. Thanks in advance. |
It fails in any request. Healthcheck just happened to be the first. But commented out and it fails on next request, a query. |
And Flutter Clean does nothing?
…On Mon, Jan 21, 2019, 06:40 Carlos Eugenio Torres ***@***.*** wrote:
It fails in any request. Healthcheck nust happened to be the first. But
commented out and it fails on next request, a query.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgn3jrU0Sb9w0K_JVq4_rBDzqoQjKSLks5vFWDNgaJpZM4aJjcx>
.
|
Okay cool. Thanks. I can see the issue and will fix later today when I am able to. Is it possible to break point line 25 of parse_response.dart. It looks as though some builds of ParseServer will response with the apiResponse.body being "OK"... As this is not happening it's trying to handle the result as if it's a ParseObject, or some extension of. I would be keep to see the response. Assuming it's just the case that some ParseServer builds might respond with "ok" in which case it's not being caught correctly. Although this wouldn't explain why some queries after are not working. Thanks in advance. |
I don't know if it helps you : https://image.noelshack.com/fichiers/2019/04/1/1548062409-capture-d-ecran-2019-01-21-a-10-16-25.png |
Thanks @scaneat . That did help... left me with more questions though. Seems as though the response isn't being handled correctly. I've created a new branch called release/1.0.9. If anybody is able to pull that and add it to their project to confirm the fix. Is everybody else having issues with more than just the healthCheck request? Again, it's not a necessary check for the app. But will be fixed in the next release. |
Parse().healthCheck() works now with 1.0.9. In main.dart, I decomment all calls in runTestQueries() : in initUser() there are still 2 littles issues in main.dart that I solved with this sample.
|
Perfect, I'll do some regression testing later and create an official 1.0.9 fix. Thanks for testing. @scaneat Do you want to create a pull request with your fixes? Or shall I add them to the release later? |
Mmm, I prefer you do it because I don't feel comfortable with that. |
Fixed in 1.0.9 |
Steps to reproduce
Description
It seems like on the request for health check, when response is returned it crashes on the
response.result = _handleSingleResult<T>(object, map);
line. I am not familiar enough with flutter and parse sdk to figure out the problem on my own yet.The text was updated successfully, but these errors were encountered: