1
App Gyver Preview App broken
complete
R
Rafael Creutz
Since Friday the AppGyver Preview App does not work anymore when we try to send data via API call to SAP CDC.
We reproduced the scenario on several devieces Android and IOS. The issue appeared after reinstalling the App Gyver Preview App. Before the reinstallation the App worked fine.
The App ID is 98003
Please support us in this issue as we have an important event for tomorrow where we need this app for a demo case.
Log In
T
Timo Kapanen
complete
T
Timo Kapanen
under review
J
Jere Robles
Rafael Creutz here is a workaround that solves the aforementioned issue: instead of using the "Error" port from the Get record node, set an If condition node that checks for the statusCode in the response body with this formula: outputs["Get record"].record.statusCode >= 200 && outputs["Get record"].record.statusCode < 400
Please note that your will have to make this adjustment anywhere you have a Data node that uses the Error port.
Let me know if this helps.
Kind Regards,
Jere
J
Jere Robles
Rafael Creutz I noticed your Login API (https://accounts.eu1.gigya.com) is returning HTTP 200 (success) regardless of whether the operation was actually successful. REST standard establishes that failed operations must return an HTTP code between 400 and 499, which is what AppGyver uses to determine whether a REST API call succeeded.
However when I try to log in or sign up with invalid credentials using the API in your app, the HTTP response is always 200, and then the _body_ of the response contains the actual error code and message as you can see in the image attached. This means that even though my request failed (because the credentials don't exist), the app thinks everything is OK because of the HTTP response code.
You mentioned this started happening after upgrading the Preview app, but could this be related to a change in the API that occurred around the same time? Do you have a way of verifying this for me?
I will continue looking for a workaround, but for now (at least one problem is that) it seems is just that AppGyver expects a REST API and the response from gigya.com is non-standard.
Kind Regards,
Jere
R
Rafael Creutz
Jere Robles: Thank you for the feedback. I have adjusted the login functionality, so it is not possible anymore to login with wrong credentials. I think this unusual behavior is done because of security, to not show the client directly of the login was not successfull.
J
Jere Robles
Rafael Creutz I'm running the app on my device, could you kindly provide some steps to reproduce the issue? Please include what did you expect to see and what are you seeing instead, screenshots are helpful, too.
J
Jere Robles
Hi Rafael, let me take a look at your app.
Regards,
Jere
R
Rafael Creutz
Jere Robles: Hi sure. Thank you for looking into this.
the steps for reproducing the issue is by clicking on sign up and register a new customer. That is where we recognize the error.
Just provide personal data and email address with password and click register.
J
Jere Robles
Rafael Creutz: see my other comments in the thread: https://tracker.appgyver.com/bug-reports/p/app-gyver-preview-app-broken Also, can you clarify what are you seeing as error? A screenshot would be nice.
R
Rafael Creutz
Jere Robles:thanks for sharing. We do not get an error code. I will try to find a way to fetch the response for SAP CDC. If I find something I'll let you know.
R
Rafael Creutz
Jere Robles: Hi, I have found the issue. It was the encode_for_url method for the email address. With this formular the preview web app and my preview app (Android) was working, but IOS stopped working.
After removing this function and just send the email address as plain text the call is successful. Seems to be the encode_for_url method which is not working properly somehow.
T
Timo Kapanen
Rafael Creutz: great that the issue got solved. I am closing the ticket as solution has been found