akirk
Connection issues with Ivory
While the Enable Mastodon Apps plugin works with a number of other Mastodon clients, Ivory for iOS still can't connect. Let's use this issue for debugging.
Helpful for debugging would be:
- Please use the latest version from this repo.
- Take a look at access and error logs of your webserver. Which requests does Ivory make?
Thanks!
Moving our testing commentary to an active thread from #7
This is the error I receive from Ivory:
@electricbrick Could you try to connect to my blog https://alex.kirk.at/ I've got error logging turned on here so I can hopefully find out what Ivory doesn't like. Thank you!
Thank you! Ivory uses a request_uri like com.tapbots.Ivory.10217:/request_token which is not a valid URL but I added support for that in ca1f7e2. I'll release a new version today with that change and many other fixes.
@akirk just tested – and it worked briefly. Turns out I was running a beta version of Ivory, but it should've expired last month. Long story short, I can't log in via the current stable release of Ivory, but have tested logins at alex.kirk.at with a number of apps so you should see those attempts in your logs. I also noticed that you added a redirect URI field to the admin screen. Mine looks like this:
com.tapbots.Ivory.13102:/request_token/XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Oh no, I should have kept the logging on. @andreasjr could you maybe also try to connect to https://alex.kirk.at so that I can get some log entries? Thanks!
@akirk Just tried it and got the same error. Let me know if you'd like me to try anything else!
Thank you, this has been very helpful. Turns out Ivory uses a grant_type client_credentials to get an app token. I haven't implemented that yet but now I know I need to.
Ivory should now work after 3fe6101344bc8bab6b801164e1c71485e31f86c0, thanks @pfefferle for testing! I've released 0.3.2 with the fix.
@akirk Thank you for the fix! Ivory now successfully authenticates with my server! However, now Ivory crashes whenever it polls the server. Not sure if that's a plug-in issue or an Ivory issue.
Oh no, likely some JSON that is returned is not to the liking of Ivory. Can you get some sort of crash report with anything meaningful in it?
Ivory is authenticating for me. I haven't tested the full range of posting capabilities however.
For everyone where Ivory crashes, could you check your access logs and identify the last request it makes? Is it consistent? If yes it might be an indicator that something in the data format of that endpoint is not quite right.
Maybe also the fixes for 0.3.3 and 0.3.4. might have helped.
I have added a new debug mode #23 in version 0.3.5 which should make it easier to see where the app crashed (i.e. which endpoint it last accessed), so if you run into this again, I hope we'll be able to find the problem more quickly!