01-15-2019 08:56 AM
Since updating our servers to update 8 on Act for web version 20.1 not a single one of our clients have been able to access the companion app. We have tested on both Iphone and Android, tested on clients who are self hosted on different versions of windows and different API methods (Connect link rather that web api) and the one thing that stays a constant across the board is update 8 on 20.1.
We can connect using the api through insomnia and on the act.web.api/swagger site and both come back successful and generate bearer tokens. Everything points towards update 8 being a cause and we have been advised to reinstall Act on the server which would mean taking down a server hosting a significant portion of our clients databases to fix and issue that we've been told is not broken.
2 weeks ago
Update on this issue that has been discovered:
I wanted to provide an update to this thread on this issue, and it's status.
The development teams for Act! Companion and the Act! API reviewed the issue, were able to reproduce and identified its root cause. The issue stemmed from a CORS implementation on the API, which changed with the last update. The issue has been resolved, and will be released with Act! Companion v2.4 (releases this month - February) and a new API build being released alongside it. You'll be notified of the new Act! Companion version via the Google/Apple app store's update feature. New versions of the API can be downloaded from https://developer.act.com/.
In the interim the issue can be resolved by updating the webconfig file for Act!/API to include both http://localhost:9595 AND https://localhost:9595.
Please let us know if you have any additional questions. If you would like early access to Act! Companion v2.4 for this fix, please email your app store email address (Google Play or Apple), and we will add you to the beta to get an early version - my email address is firstname.lastname@example.org. Beta will be available early next week.