The request headers will actually get set to something if I do this
and the output I get is this
Sorry for so many large pictures
and the output I get is this
Sorry for so many large pictures
That doesn't make any sense.....
This is the recommended format:
why are you headers not getting set ?
I think that's the million dollar question. When I use the recommended format I get error 1111 and when I use the other random format it sets the headers, they just don't work. I also tried doing this
But it just goes straight back to the error 1111
Beware of the not blank but instead empty text box.
AI2 trims trailing blanks, and you have to go back and insert them.
You have a private message....
Well I setup a yelp account and got an api key.
Ran your url with these blocks
and here is the return, data as requested....
2 Likes
Tested with your api key and it also returns data
Huh. what could be different on my end. Maybe if I set a variable for token?
Try with just the blocks that I have used...
(successful sample added to FAQ)
I don't understand I've done everything the same and it still doesn't work.
If its not the code that's the problem or the key, could it be the phone I'm using or the version? I updated the companion app to version 0.9 in test flight. I'm using an iphone SE to test it.
Ahh
I know nothing of ios or test flight.
Suggest you try an android phone ?
I'm looking into the possibility that its my network or something. I'm stuck with an apple phone unfortunately. I guess I'll post back here if I fix my problem if not I'll just drop it and do something else.
Alright I think I figured it out. It works on android phones and not ios. I had a different friend test it out with his android phone and it worked fine, but when he tested it with his iphone it doesn't work. It was the exact same code and internet connection just a different testing device so I think that has to be it.
If you send me the AIA that works on Android, I can run some analysis on the iOS version and see what's going wrong.
aia sent via PM
Thanks @TIMAI2. I've identified the problem and have come up with a fix. It'll go out in the next iOS version.
When do updates come out usually if you don't mind me asking?