Skip to content
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

Fetch : talk about response.headers.map in the doc + iterator exception #13450

Closed
ancyrweb opened this issue Apr 11, 2017 · 1 comment
Closed
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@ancyrweb
Copy link

ancyrweb commented Apr 11, 2017

I'm using Fetch in my project and i've come to realise that when using standard developer mode, I cannot use Iterator to loop through the entries of the Header object, but a "map" object is provided in the header. When i'm starting the JS Debugger with Chrome suddenly the entries iterator works. Maybe the fetch API relies on Chrome when Debugging and Native when it's not, but it's been weird to track the Iterator exception because my first feeling was that no matter the context (Chrome or Native) the fetch API is the same.

The error I get when trying to make a for...of is : "TypeError : undefined is not a function (evaluating '_iterator[typeof Symbol === 'function' ? Symbol.iterator : '@@iterator']()').

@hramos
Copy link
Contributor

hramos commented May 31, 2017

Hey, thanks for reporting this issue!

It looks like your description is missing some necessary information. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.

I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!

@hramos hramos closed this as completed May 31, 2017
@facebook facebook locked as resolved and limited conversation to collaborators May 31, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

3 participants