Getting error detail

#1

I think it would be great to have more detailled error messages.
More than “Messenger App couldn’t be loaded”

ex: “invalid sheet, ‘url’ is missing”

When you develop your app for the first time, it’s a good way to get on the tracks.

When you get back on your app a few weeks later and the way it works is not fresh in your might, that relieves a lot of frustration and helps to get back in the tracks.

Note that detailled messages should be limited to apps in ‘staging’ or ‘beta’ mode.

2 Likes

#2

Hey @Mose thanks for that feedback! That’s really useful. @hellojeanpierre this might be useful feedback for you :+1:

However, just a quick heads up, on your webserver where you’re handling the Messenger App, there’s a good chance that the error should surface there.

For example, in the Rails app that I have for putting apps together, if the app itself doesn’t work, it should come up in server logs :point_down:

Started POST "/example_app/initialize" for 127.0.0.1 at 2018-04-27 11:37:46 +0100
Cannot render console from 172.17.0.1! Allowed networks: 127.0.0.1, ::1, 127.0.0.0/127.255.255.255

ActionController::RoutingError (No route matches [POST] "/example_app/initialize"):
0 Likes

#3

We don’t have yet a concept of staging or beta mode apps, something we’re looking at.

Totally, better error messages are super valuable. cc/ @patrick.andrews

0 Likes

#4

Thanks Jonny,

Yes, checking the server works for routing errors, but in my latest case, the problem was I used an http URL in a sheet flow (instead on an httpS one). I struggled for an hour and re-read the whole doc before getting the solution !

By the way, allowing http for sheet flow for the future ‘staging’ mode would be nice too :wink:

1 Like

#5

I need this as well. I’m getting an error and I have no idea what it is.

0 Likes