type '_InternalLinkedHashMap<String, dynamic>' is not a subtype of type 'ParseBase' #42

jellyninjadev · 2019-01-20T09:35:09Z

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.

The text was updated successfully, but these errors were encountered:

phillwiggins · 2019-01-20T09:37:06Z

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> .

phillwiggins · 2019-01-20T11:11:35Z

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> .

jellyninjadev · 2019-01-20T15:34:46Z

Hey @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

abstract class ApplicationConstants {
  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

I just run from examples folder, so I guess my library version is master.

phillwiggins · 2019-01-20T15:40:27Z

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> .

erickvasilev · 2019-01-21T00:19:58Z

I got this error after init:
var response = await Parse().healthCheck();

parse_server_sdk: ^1.0.8

My Parse server is configured correctly and running, I'm using it for my Web App.

cetorres · 2019-01-21T01:39:52Z

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.
I cannot even start my app. Please fix it asap.
Thank you.

phillwiggins · 2019-01-21T05:53:47Z

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> .

phillwiggins · 2019-01-21T06:05:46Z

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.

cetorres · 2019-01-21T06:40:12Z

It fails in any request. Healthcheck just happened to be the first. But commented out and it fails on next request, a query.
Thank you for the attention!

phillwiggins · 2019-01-21T06:54:38Z

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> .

erickvasilev · 2019-01-21T07:09:01Z

Hi, not sure how to add a breakpoint in Flutter, but the server response is {status: ok}

phillwiggins · 2019-01-21T08:30:22Z

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.

ghost · 2019-01-21T09:20:36Z

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

phillwiggins · 2019-01-21T09:26:40Z

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.

ghost · 2019-01-21T09:43:31Z

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.

// Returns type ParseResponse as its a query, not a single result
    response = await ParseUser.all();
    if (response.success) user = (response.result as List<dynamic>).first as ParseUser; //(ISSUE) response.result;

    var queryBuilder = QueryBuilder<ParseUser>(ParseUser.forQuery())
      ..whereStartsWith(ParseUser.keyUsername, 'phillw');

    var apiResponse = await queryBuilder.query();
    if (apiResponse.success) user = (response.result as List<dynamic>).first as ParseUser; //(ISSUE) response.result;

phillwiggins · 2019-01-21T09:46:19Z

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?

ghost · 2019-01-21T09:48:24Z

Mmm, I prefer you do it because I don't feel comfortable with that.

phillwiggins · 2019-01-21T18:12:40Z

Fixed in 1.0.9

phillwiggins closed this as completed Jan 21, 2019

phillwiggins mentioned this issue Jun 18, 2019

Best strategy for testing my app #202

Closed

jeansebastienZ mentioned this issue May 11, 2020

SDK Parse 1.0.26 not usable - boolean expression must not be null #371

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

type '_InternalLinkedHashMap<String, dynamic>' is not a subtype of type 'ParseBase' #42

type '_InternalLinkedHashMap<String, dynamic>' is not a subtype of type 'ParseBase' #42

jellyninjadev commented Jan 20, 2019

phillwiggins commented Jan 20, 2019 via email

phillwiggins commented Jan 20, 2019 via email

jellyninjadev commented Jan 20, 2019 •

edited

Loading

phillwiggins commented Jan 20, 2019 via email

erickvasilev commented Jan 21, 2019 •

edited

Loading

cetorres commented Jan 21, 2019 •

edited

Loading

phillwiggins commented Jan 21, 2019 via email

phillwiggins commented Jan 21, 2019

cetorres commented Jan 21, 2019 •

edited

Loading

phillwiggins commented Jan 21, 2019 via email

erickvasilev commented Jan 21, 2019

phillwiggins commented Jan 21, 2019

ghost commented Jan 21, 2019 •

edited by ghost

Loading

phillwiggins commented Jan 21, 2019

ghost commented Jan 21, 2019 •

edited by ghost

Loading

phillwiggins commented Jan 21, 2019

ghost commented Jan 21, 2019

phillwiggins commented Jan 21, 2019

type '_InternalLinkedHashMap<String, dynamic>' is not a subtype of type 'ParseBase' #42

type '_InternalLinkedHashMap<String, dynamic>' is not a subtype of type 'ParseBase' #42

Comments

jellyninjadev commented Jan 20, 2019

Steps to reproduce

Description

phillwiggins commented Jan 20, 2019 via email

phillwiggins commented Jan 20, 2019 via email

jellyninjadev commented Jan 20, 2019 • edited Loading

phillwiggins commented Jan 20, 2019 via email

erickvasilev commented Jan 21, 2019 • edited Loading

cetorres commented Jan 21, 2019 • edited Loading

phillwiggins commented Jan 21, 2019 via email

phillwiggins commented Jan 21, 2019

cetorres commented Jan 21, 2019 • edited Loading

phillwiggins commented Jan 21, 2019 via email

erickvasilev commented Jan 21, 2019

phillwiggins commented Jan 21, 2019

ghost commented Jan 21, 2019 • edited by ghost Loading

phillwiggins commented Jan 21, 2019

ghost commented Jan 21, 2019 • edited by ghost Loading

phillwiggins commented Jan 21, 2019

ghost commented Jan 21, 2019

phillwiggins commented Jan 21, 2019

jellyninjadev commented Jan 20, 2019 •

edited

Loading

erickvasilev commented Jan 21, 2019 •

edited

Loading

cetorres commented Jan 21, 2019 •

edited

Loading

cetorres commented Jan 21, 2019 •

edited

Loading

ghost commented Jan 21, 2019 •

edited by ghost

Loading

ghost commented Jan 21, 2019 •

edited by ghost

Loading