How do I make the “Update” button appear in BitBucket for our plugin? I have updated my descriptor, and would like the users to see the new options, however existing users don’t get it until they press Update, but the “Update” button does not appear for my app.
I have tried to bump the version in the descriptor, and create a new release on MarketPlace with a matching build number, with no effect.
Ensuring that the “Update” button appears for your Bitbucket plugin involves a few steps, and it’s great that you’ve already updated your descriptor file. Here are some suggestions to troubleshoot and resolve the issue:
Increment Version in Descriptor: Make sure you’ve properly incremented the version number in your app’s descriptor file. This is crucial for Bitbucket to recognize that an update is available. Ensure that the version number is higher than the previous one.
Check Descriptor Syntax: Verify that your descriptor file is correctly formatted and adheres to Atlassian Connect specifications. Any syntax errors might prevent the update mechanism from working as expected.
Create a New Release: You mentioned creating a new release on the Marketplace. Confirm that the release you created corresponds to the updated version in your descriptor file. The version number in the Marketplace release should match the version in the descriptor.
Review Atlassian Connect App Licensing: Ensure that your app’s licensing configuration allows updates. If there are restrictions in place, existing users may not see the “Update” button.
Clear Browser Cache: Sometimes, the browser cache may cause issues in displaying the updated interface. Advise users to clear their browser cache or try accessing Bitbucket in an incognito/private browsing window.
Verify Marketplace Settings: Double-check your app’s settings on the Atlassian Marketplace. Ensure that everything is configured correctly, including the compatibility of the app with the Bitbucket version.
Check Bitbucket Compatibility: Confirm that your app is compatible with the Bitbucket version your users are using. If there are compatibility issues, the update button may not appear.
Inspect Bitbucket Logs: Review the Bitbucket logs for any error messages or warnings related to your app. This might provide insights into why the update button is not appearing.
Test with a New Installation: Try installing your updated app on a Bitbucket instance where it hasn’t been installed before. This can help determine if the issue is specific to existing installations.
Contact Atlassian Support: If the issue persists, consider reaching out to Atlassian support for assistance. Provide them with details about your app, the steps you’ve taken, and any error messages you’ve encountered.
By carefully going through these steps, you should be able to identify and resolve the issue with the “Update” button not appearing for your Bitbucket plugin. In my case I took help from triotech systems. For yours I just asked AI. lol but do try and let me know if it works
The app descriptor can only be updated via REST API if the app descriptor does not change scopes.
A simple pattern could be to store the app version in a simple property, compare with the new descriptor version and send the PUT request to BBC to update the descriptor automatically, then store the updated version property.
If your app is distributed through the Bitbucket cloud marketplace that you can access in workspace settings, and users install your app from the BBC MP it’s technically impossible to update app scopes unless your re-install the app. Note that all properties stored by the app are lost.
If you don’t distribute the app via MP you can register an app and distribute the link to your customers. In this mode customers that use the app can update through in workspace settings > Installed apps