Android Studio updates

[jhaynes]

Hi all,
I have a 2 part query.

Query 1
I recently had some users complain about getting an error (attached) with Android studio when opening which I later found was due to PMP pushing the latest version of Android Studio.

So, to give context it seems when an older version of Android Studio is installed which in our case is Giraffe | 2022.3.1 (Not verified if the error occurs with any other older versions, just Giraffe atm)

Patch my PC would deploy the latest Android Studio version which as of now is Ladybug | 2024.2.1
When this happens upon opening Android studio you would get the attached error, which seems related to a plugin.

However, should this type of updating happen? Shouldn't PMP only update the current version? So, essentially only push build updates in this case for Giraffe | 2022.3.X
From what I can tell, as it's not obviously clear looking at Android Studio Developer Releases the below versions are technically still in support and getting periodical updates?

Ladybug            | 2024.2.1
Koala Feature Drop | 2024.1.2
Koala              | 2024.1.1
Jellyfish          | 2023.3.1
Iguana             | 2023.2.1
Hedgehog           | 2023.1.1
Giraffe            | 2022.3.1
Flamingo           | 2022.2.1

Either way if this is expected, the users that are complaining about this error are actually required to stay on the Giraffe version of android studio. So, I have had to employ a exemption by setting up another ADR and collection.

Query 2 - following on from just above
Which by the way seems a rather excessive way of excluding specific machines from a specific update but the only way I know it can be done. Unless there is a better way I don't know of?
 
I read these two docs on exemptions that helped me setup exemptions.
How to Use Automatic Deployment Rules (ADRs) with Patch My PC Updates
How to Remove Already Published Third-Party Software Updates

But in our estate/environment where we have multiple studios and many projects, often some projects require staying on specific versions or builds of apps/software. So, were going to end up with quite alot of PMP ADRs just for exemptions.
This also requires ensuring that with any new exemptions, checking the machines are not part of any existing ADRs/collections. Which is why it seems rather extreme if you get where I'm coming from?

So in a constant battle of keeping machines patched this becomes a headache, so is employing ADRs with filters the only way to exclude a group of machines from a specific update due the the limitation of using ADRs?

Regards,
James H

[Andrew Jimenez (Patch My PC)]

Hello,

We will likely have Android Studio renamed to "Android Studio Latest" so that the update title is more accurate according to our naming standards: https://patchmypc.com/products-multiple-versions-patch-my-pc

Unfortunately, we will not be offering the previous versions at this time, as we already have many difficulties with this application due to the way they register their application in the registry. It also seems like your environment may be quite unique as Google recommends on this page: https://developer.android.com/studio/archive to use the latest version.

I think your best bet will be to have a collection of devices that can stay on the latest Android Studio version, and only deploy Android Studio updates to that collection. The other devices would need to be self-managed, or you could create installation packages for those devices.

[jhaynes]

Hi Andrew,

Thank you for replying. Yeah our environment is certainly abit more unique annoyingly. But thanks for clearing that up in regards to the updating of Android Studio as I will have to inform our Security team this will likely be a permanent thing.

Yeah I have made a collection of devices we want to not have android studio patched for now and created a new ADR to filter out that update.

Thanks again for the info.
Regards,
James