@MichalDanielDobrzanski thanks!

TBH, I'm not sure if the link in the description provides enough evidence for this change...

In fact, some people might have to add aar files to the default app/libs directory. If aar files are excluded by default, they won't show up in git status.

On the other hand, if you're talking about build output, then those files are contained in the build/ folder - which is already part of this .gitignore, meaning there is no real value in adding *.aar. This (amongst many other things) is taken care of in #2402

@friederbluemle thanks for the feedback. @MichalDanielDobrzanski do you agree with this?

I agree that some aar files land in libs folder.

However, the usual flow does not assume adding to Git compiled dependencies (due to their size or specific versioning). They are downloaded by default and checked out from VCS.

We can revert this, though.

We can revert this, though.

I have no strong feelings either way on this, so I'll leave it up to @friederbluemle and @MichalDanielDobrzanski to figure this out and submit a follow-up PR (if necessary).

Yes, also agree with @MichalDanielDobrzanski that compiled dependencies should normally not be added to version control. Normally these files are all contained in build/ (which is already ignored). So we can revert this. It is already taken care of in #2402 - @shiftkey please take a look. And @MichalDanielDobrzanski as well, in case there is anything to add. Thanks!!