Open kkohno opened 1 year ago
This issue does not seem to follow the issue template. Make sure you provide all the required information.
Hi @kkohno,
Thanks for reporting this issue. I've used the sample project you provided, and I wasn't able to encounter this issue on the first try. A different error message appeared, but it went away after enabling Custom Gradle Properties Template
. However, I should mention that I used the editor's latest LTS version (2021.3.16). While I try using the sample project with the version you specified, could you try using the aforementioned version and see if this would be applicable to your use case?
we encountered this bug a long time ago, long before version 2021.3.16. this version reproduses the same bug. Note, the bug can be reproduces on windows. It seems, that Path.GetDirectoryName works different on windows with directory names, that includes dots, and parsed as filename
I suspect this or this lines has unexpected behaviour with directory names such as 0.11.01 on windows
Has reinstalled the project again from scratch. Reproduce steps 1 download project from repo 2 switch to android 3 call: Assets->External Dependency Manager->Android Resolver->Force Resolve (seems without bug, however error log) 4 repeate step 3
Thanks for the update, @kkohno. I just realized that you're on a Windows machine while I was testing using macOS. Just tested using version 2022.2.1f1 on a Windows machine, and I was able to replicate this behavior. I'll be relaying my observations to the team about this. For now, let me mark this as a bug.
ok, thanks
Seems like @paulinon can reproduce this on Windows machine.
Hmm, I was expecting https://github.com/googlesamples/unity-jar-resolver/commit/ad55ee64e6bbd7e86b2bd650bf2c81b87917724e to fix this issue already. This should be part of 1.2.175
.
I suspect that AssetDatabase.CreateFolder()
or Directory.CreateDirectory()
behave differently in this version of Unity on Windows. We can take a look.
will be good
I suspect that
AssetDatabase.CreateFolder()
orDirectory.CreateDirectory()
behave differently in this version of Unity on Windows. We can take a look.
I face this bug with many versions of unity 2022 on Windows
I solved the same problem, but I'm not sure it would help displaying Ads on device(I'm still testing). It seems when you press 'Force resolve' the resolver makes the folder name something like 0 or 0 1 or..so on. But the those folder name should be 0.11.01 as they say on the error, the path from the 'GooglePlayGames' and 'GeneratedLocalRepo' should be the same. After you modify the name of the folder then press the 'Force Resolve' then I would say succeed. However, If you just 'Resolve' again, the same problem will occur, so I'm not sure it would really work.
I solved the same problem, but I'm not sure it would help displaying Ads on device(I'm still testing). It seems when you press 'Force resolve' the resolver makes the folder name something like 0 or 0 1 or..so on. But the those folder name should be 0.11.01 as they say on the error, the path from the 'GooglePlayGames' and 'GeneratedLocalRepo' should be the same. After you modify the name of the folder then press the 'Force Resolve' then I would say succeed. However, If you just 'Resolve' again, the same problem will occur, so I'm not sure it would really work.
Yes, it is solve problem, if rename directories manually. But another force resolve requires manually renamings again... It's annoying and not everyone will think of renaming folders.
Hi, Any update on this?
This plugin is so broken, I already tried everything
Hi, any updates? @cristianjuarezz @ahmedameen2 @kkohno I have just to put this "0.11.01" instead of the folder named "0" everytime or there is another way? Please
[REQUIRED] Please fill in the following fields:
[REQUIRED] Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
Please answer the following, if applicable:
What's the issue repro rate? (eg 100%, 1/5 etc) 100%
What happened? How can we make the problem occur?
It is can be fixed if created folder name("0" see screen) manually rename to 0.11.01.
Mminimal project to reproduce