Android studio is still a half turd ( electric eel )

[gilesgoat]

I don't know if the problem lies on "I am trying to support too many things at once" and/or "it evolved like that and there's no way any more to fix it" ..

Also "whatever documentation seems to be at least 6 months ( if not more ) behind the current version".

So once more again I am into ( studying for now ) "Oculus ( Meta ) Native Development" ..

And once more again I was into "follow the setup instructions" .. and NOR the instructions NOR the current version of Android Studio ( Electric Eel ) are up-to-date aligned with each other.

Also got the impression that "whoever wrote them had maybe Linux, maybe Mac but NEVER touched Windows" .. and things are NOT the same OH NO ..

Anyway when you have instruction saying "download Android Studio" WITHOUT specifying WHAT damned version you talking about ? And EVEN WORSE Android Studio Setup ITSELF !! Saying things like " .. and after you finished setup define ( for example ) this sys var JAVA_HOME to the location of .. that SHOULD BE <weird path> " .. and guess what ? TURNS OUT THAT SHOULD BE WAS TOTALLY INCORRECT !!

I *SUSPECT* in Linux MAYBE it was pointing to a dir/place with some "symlink" that maybe pointed to all else ? .. I'll never know NOR after spending HOURS trying to see "where that place could be" and no it wasn't "jre/bin" .. turns out it was "jbr/bin" .. wtf is the difference ? One dir is totally EMPTY, one has "something" ..

So 3 FUCKING DAYS of trial & error, massive internet searches, "imagination" and OBSCURE ERROR MESSAGES ..

They FORGOT to say that "oh in Windows you DO NOT HAVE PYTHON by default" and basically "add EVERYTHING to the path" OR even if I just made you defined some "sysvars" that has some paths .. it would appear that "I don't care about those really".

Then, well thanks to the soul that made it, had to follow A YT VIDEO about "How to open and run the oculus samples" ...

I've seen shit but "that beats them all" ..

So you download the samples .. can you open/compile/run them ? NO FUCKING NO WOULD BE TOO EASY !

No because you have to DRAG AND DROP an icon .. then open ONE specific gradle.init file in ONE specific folder .. and then you have to go inside every damned OTHER sub-project folder and open another gradle.init file COPY OUT ONE PARTICULAR LINE and PASTE IT INTO THE OTHER FILE and DO THE SAME FOR ALL THE PROJECTS ..

Then you have to save and hit "SYNCH WITH GRADLE" and after too long time .. it still won't work ..

Your version of "Gradle Plugin" or some other shit "won't match the one needed" .. follow HUNDREDS OF MEGABYTES of download/setup/shite/etc ..

And so probably "for a few more things" every time you'll re-try to compile it.

Then you'll find out that unless you hit the icon "play/run" in a particular place, that will make ONE single "sub project" and launch it the "make all" doesn't work ( tries to link with a lib that seems not to be there and/or maybe not in the right path ??? ) ..

But then it still crashes .. if you forgot to disconnect/reconnect/say "allow" to the oculus device ..

And this works with some of the NEW samples .. however .. if you try the "older ones" ( which still contains the ONLY Vulkan Sample ever made still signed by a person that is long dead and another one that is long gone from Oculus probably ) they won't work, because they look for a keystore that does not exist.

And probably more versions of more pacakages that don't match the ones the project "wants" ...

Then you have to generate your own keystore and manually go and modify the "package signature" or it won't be able to generate any "APK" ..

The thing is every step you just get something that "doesn't work" and you don't really know WHY or WHAT, in SOME RARE CASES you get some error message that at least "says something" in most cases just "nothing happens" and you don't have a clue.

I never seen anything with "a much overbloated UI, tons of shit to configure, lot of mess to in the end just "compile & link & make a .apk" ..

It's a MASSIVE PAIN IN THE ARSE to set it up.

Fingers crossed it'll remain working, and I yet have to figure out how to create "A new Meta project" ...

Probably another week of swearwords needed.