Updating extension in console UI replaces original config

[READ] Step 1: Are you in the right place?

not sure if it’s the right place to report issue for Firebase Console UI (Extensions)

[REQUIRED] Step 2: Describe your configuration

• Extension name: Firebase console UI/Extensions

[REQUIRED] Step 3: Describe the problem

Starting extension update in firebase console UI while there is another update of same type is in progress - configuration for new update will be overwritten with config from those one which is updating.

Steps to reproduce:

1. 2 firestore-bigquery-export-instances extensions deployed for 2 different firebase collections.
2. start update of 1st extension
3. complete step-by-step update walkthrough with the last step - “configuration”
4. configuration has proper values
5. start updating of 2nd extension
6. step-by-step walkthrough is automatically closed and update started
7. when update is finished - 2nd extension will use configuration from 1st instance

I’ve got this issue twice. Updating 0.1.1 -> 0.1.2, and today with 0.1.2 -> 0.1.3

Expected result

Console UI should work properly with multiple instances of same extension

Actual result

[russellwheatley]

Ok, gotcha. I was able to get the “update is available” option once I installed the previous version 0.1.2. I was also able to reproduce the bug. Thanks for reporting it, @stari4ek.

Hey FE team, this is a bug in the console UI. Steps to reproduce:

• Install two firestore-bigquery-export extensions, version 0.1.2.
• Head over to the firebase console extension’s tab and click on either one of the new extensions. In the top right hand corner, you’ll see an option to update extension. Click it, and change the collection property and the table id prefix property.
• The extension will start updating. It will also start updating the other extension on version 0.1.2 without you editing it.
• Once both extensions have finished updating, you’ll note that they now have the same config.

[tjlav5]

@stari4ek thanks for posting! Turns out there was a memory-leak in the dialog which could affect subsequent dialog instances 👎 This should be fixed in the Console now.