I’d like to use an EAS webhook to post a Slack notification for succesful adhoc builds. For these builds, I’d like to display the install link in the Slack notification (or better yet, the QR that’s shown when you select install on the build details page).
Using the appId and id fields, I can construct the install url (itms-services:// etc. etc.) manually, but it would be nice if it was included in the artifacts array.
Bonus points for including a QR image URL as artifact
One other thing I cannot find out, is whether the build is in fact an adhoc build or not, from the metadata in the webhook. Is there any way to determine this?
In addition: the buils details page URL would also be great. In case of an errored build, I’d like to put a link to the build details in my notification, and I need to manually construct that one now, which is not straightforward (account name is only in the URL when it’s different from username for example).
Hey @kbrandwijk, thanks for taking the time to write up some feedback and give us your ideas on how to improve the EAS flow. Let me relay this internally and see where the team would like to collect/track EAS feedback.
(Saw your other two posts as well. Holding off an responding in them until we know the best path forward!)
Thanks @adamjnav, that sounds like a plan. The missing versionCode for Android builds is a bit of a showstopper though, as I have no way to report back on the version of the build on Android without it.
I have workarounds for everything else in this post at least, because for now, I’ve manually constructed the install URL, use a free online service to generate the QR on the fly, and manually generate the build details URL, and I’m using the buildProfile name to ‘know’ if it’s supposed to be an adhoc build (though hardcoded).
Hi @kbrandwijk . I am looking for the method to get the install URL along with QR code for successful builds triggered by our automated CI pipeline and upload them into S3 bucket for internal sharing between team members. I am wondering if you can share with me the details of your workaround solution your mentioned above.