getFeatures pagination failure

[zanetaylor]

When attempting to construct an array of features in a pagination loop, I'm encountering perhaps related problems with the pageSize and pagination params for the getFeatures method.

1. Using an explicit pageSize param always throws a postMessage console error: Error fetching features: could not convert string to float: ''
2. Without an explicit pageSize param, the method returns the first 20 features as the expected default, but passing the response's nextPage key to subsequent calls always returns the same / first 20 features instead of the next page.

[tomhicks]

Taking a look at this today. Thanks for reporting.

[tomhicks]

@zanetaylor this should now be resolved by changes on the felt side, no SDK changes necessary. Can you please test this in your app, and let us know if you're still having problems?

If it's all good, I'll close this issue.

If you are still seeing problems, it would be helpful if you could provide an example of the exact SDK calls that are not working as expected, along with the map ID that you're operating on so we can test directly.

Thanks!