prompt before auto resolution does not work as expected

[Thaina]

I expect that prompt before auto resolution option would just launch popup to ask for skip when auto resolution would occur. But it just ask for enable or disable auto resolution and it always disable itself after popup once

Is it a bug? If it not I think it useless. Please add the actual functionality to let us skip auto resolution. It would be useful when we add many unity packages and then let it resolve after last package

[stewartmiles]

@Thaina I believe this feature was added to enable folks to disable auto-resolution when importing the first of a series of packages, then they can enable auto-resolution or just force resolve when they're done. You would prefer to see a prompt pop up for every auto-resolution attempt? That would only then prompt the developer if the dependencies change again.

[Thaina]

@stewartmiles Let me ask one thing

What is the time when we should go in the setting and toggle the prompt before auto resolution to on?

I thought it would be a time that we have nothing to import, but feel like there would be in the future. And so we must open the setting panel to toggle it for anytimes in the future

And if any dependency was changed by anything around this time, the popup will launch. We press anything and then it will disable itself

And then when there would be a time we need to import many packages. We try to import one, and if the last time we press enable, the resolution will kicking after we import the first package

If my above guess is right, then this feature would hardly be used. We rarely know in advance that do we need to enable this popup for the future when most of the time we would import only one package. This feature is important only we import more than one at once

If we need to remember to toggle it on after we import any package or has any package changed by any means. It would not be much difference to just disable auto resolve and just remember to always resolve dependency manually. So I think this feature is totally useless

It would be more useful if it always enable to guard us off of the auto resolve that cause a friction and annoyance of importing multiple package instead of got stuck on resolving dependency

I think the user experience flow of the package importing is, if we have multiple package in the queue in our mind, we import one, and wait for import process finish to import another. We still having focus on our input device and so just another popup to ask that do we need to resolve dependency now or not is fine. We just click cancel and import next package, until the last package and we click yes

[Thaina]

And also. If you would implement this feature. I would like to recommend that, this popup should have timer around 10 sec to just auto resolve

The use case of importing package is, we might just import large package and then AFK while enable this popup. So we would be more likely to have everything done when we get back

[stewartmiles]

The use case is:

• Developer imports a plugin 1
• Resolution prompt pops up
• The developer is importing multiple plugins so disables auto-resolution
• Developer imports plugin 2..N
• After importing all plugins the developer goes to the Android Resolver settings, enables auto-resolution which then runs resolution.

I realize that you're asking for something different which prompts for resolution after importing each plugin in turn. Sounds relatively easy to implement but it does add to the confusion when combined with the existing dialog. I guess a multi-select dialog could pop up instead that provides the 3 options:

• Resolve
• Skip resolution
• Disable auto-resolution

In your case you could click Skip resolution, and the folks we built this feature for could click Disable auto-resolution instead.

WDYT?

I'm not sure about the count-down. Firstly, it requires yet another custom window to build this which would race with the plugin import. If resolution starts and the developer manages to import a plugin at the same time which reloads the app domain it's very likely going to end up in a bad state.

Anyway, if you want to send a pull request the code is here

unity-jar-resolver/source/PlayServicesResolver/src/PlayServicesResolver.cs

Line 1471 in e703601

if (GooglePlayServices.SettingsDialog.PromptBeforeAutoResolution &&

[Thaina]

@stewartmiles

The use case is:

Developer imports a plugin 1
Resolution prompt pops up
The developer is importing multiple plugins so disables auto-resolution
Developer imports plugin 2..N
After importing all plugins the developer goes to the Android Resolver settings, enables auto-resolution which then runs resolution.

I have understood this use case from the start. But what I ask you is, this feature will be toggle off itself after this one time use

When will you think it will get toggle on again?
When your popup launch. The user press disable. Then import all package. Then go press auto resolution. Wait for resolving finish. Will they think they should go toggle this feature to on again?

4 reason I think they won't

• They don't remember to
• They think they don't need to. They think they would not import multiple package again (but sometimes they will, in the future, and they don't know)
• They don't know it was toggle off everytime this popup launch
• They just like me and they would just disable auto resolution and manually go to resolve menu

In your case you could click Skip resolution, and the folks we built this feature for could click Disable auto-resolution instead.

What I expect in my case is, I would not need to go to menu and press resolve manually. And I don't need to go enable anything again just because I need to import 2 packages today. If I import one more package tomorrow the auto resolution will still be on

But with the current UI. Even if we enable it today because we hope that tomorrow we would need to import multiple package. But we might have only one package need to be imported tomorrow. So we enable auto for that package, wait till finish, then we need to go toggle it again

In fact, with the current UI process, it require the same amount of interaction we need to do as we just disable auto resolution and use force resolve menu manually. If we need to remember to toggle it on everytime we import any package then isn't it easier to just disable both this feature and auto resolution then just remember to resolve after import package? So it actually really useless

I don't like to disable auto resolution because I want it to always resolved when any dependency changed. But it just when we need to import multiple package the auto resolution will create too much friction. However to disable it all is not great

As I describe my user experience flow in previous comment. I think auto resolution should always be enabled by default and should never be disabled. My propose idea is to have option to delay it, just when we need to import more than one package

[Thaina]

@stewartmiles I try to clone this repo but there was no guide to start develop this repo. Open with Visual Studio throw 900 errors. And Unity cannot open this project in its editor

[Thaina]

@stewartmiles I have create pull request #219 but I don't really know if it can compiled or really worked because I still cannot open this repo properly but it doesn't changed much so just hacking the code directly

[stewartmiles]

Oh I missed this, to build / test follow the instructions here https://github.com/googlesamples/unity-jar-resolver#building-from-source

[Thaina]

@stewartmiles Do we have a way to run the code directly in unity? So we could debug and so on

[stewartmiles]

@Thaina not really, the build needs to pack files into the DLL etc. I typically iterate by doing...

./gradlew compileAndroidResolver && cp ./build/PlayServicesResolver/bin/Google.JarResolver.dll* ./path_to_unity_project/Assets/PlayServicesResolver/Editor

[patm1987]

There hasn't been any activity on this thread so I'm closing it for now. If we didn't resolve the issue to your liking or you have more information to give us feel free to re-open this with a comment or create a new issue referencing this one.

--Patrick