Custom Action Working in Preview but not in Testing

3rd party APIs are not working

No, they are. I’ve tried other ones.

@John can you try writing the response directly on the screen and see if there’s a value being returned from your API?

I have had a similar issue previously and when I tried to print the result directly on screen without first storing it in the list, I realized that the reposes were blank.

If I try to edit any 3rd party api collection, it does not work. Also, if I build a new version for iOS or Android, none of the data shows up in the app. This is very disturbing. Oddly, the apps that are in the app store are working. I haven’t changed anything in my app other than redesigning the login page and changing the url to 1 static image. There is something odd going on that doesn’t make sense. The web preview application works fine though.

1 Like

I just created a new project, then added an external collection with a test JSON webservice. It will not let you add it. try to do it yourself.

URL:
https://jsonplaceholder.typicode.com/todos/

UPDATE MORE INFO, In console:

Yeah, I tried that and wasn’t getting anything. But that’s the weird part. It works when it’s testing but not when I run it.

Thanks. That’s weird, I thought that was the whole idea of custom actions?

@Colin, any thoughts?

This could be due to the onscreen action not passing the data to your custom action. You can try to re-run this while the inspect mode on your browser is turned on to check is the status codes are returning 200.

That could be one way of identifying where this is breaking.

1 Like

@bhanu thanks

@John glad that helped, maybe one last check I could think of to do is to print the api_key on your screen above the button to see if the logged in user api-key is actually being sent when you click the search domain for emails button.

1 Like

Figured it out. I wasn’t logged in. So if you want to test with data from logged in user do you always have to log in? So you can’t test with setting the screen as “if user is logged in”?

1 Like

Yup, you must be logged in to pass any logged in user data during testing (preview mode).

Glad you could get to the root of it. Cheers!