Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up & Update gradle config #15

Closed
wants to merge 7 commits into from
Closed

Conversation

Doomsdayrs
Copy link

A minor clean up to get things working properly, as sync seemed to have failed otherwise.

Do ignore the name of the branch

Please do note that the project fails to build the JVM target for some reason

@Doomsdayrs
Copy link
Author

Figured out why it was not compiling

minSdkVersion(21)
targetSdkVersion(29)
minSdk = 21
targetSdk = 31
Copy link
Owner

@g0dkar g0dkar May 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, sorry for taking this long to answer, either GitHub didn't notify me or I missed the notification :(

Anyway, thanks for the contribution! My only question is about the targetSdk. Any reason for bumping it from 29 to 31? It's been a looooong time since I developed for Android so I don't remember what it'll affect in the end. If it doesn't affect much, I don't see why not.

[Edit for clarification: I just want the library to be compatible with the most devices possible, since it doesn't do much that isn't supported from Android 1.0]

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

31 is for android 12
32 is for android 12L

Its best to target the latest releases at all times, and always maintain the latest min version.

@shalva97
Copy link

Any news on this PR? I also can not build the project

@@ -7,10 +7,14 @@ dependencyResolutionManagement {
}

pluginManagement {
repositories {
google()

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also needs mavenCentral() here, otherwise fails with
Could not GET 'https://jcenter.bintray.com/....'. Received status code 502 from server: Bad Gateway

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heya!

Could you try with the version up on main right now?

I've addressed these and some other changes there some time ago. For example, here's mavenCentral() on settings.gradle.kts: https://github.com/g0dkar/qrcode-kotlin/blob/main/settings.gradle.kts#L3-L5

If it still doesn't work, please let me know! :D

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is strange, how does it work on your side?

For me it fails on Plugin [id: 'com.android.library', version: '7.2.1', artifact: 'com.android.tools.build:gradle:7.2.1'] was not found in any of the following sources too.

Also the mavenCentral you mentioned is for the project dependencies, not for plugins

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I see!

Everything is working here 🤔

I think I know why it is working here tho: some shenanigans I have to have in place for my work. Let me comment those and try again!

Thanks for bringing this into light! <3

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, it WAS the stuff I had in place for work 🤦

I'm committing the fixes right now! Thanks again for reporting on this!

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I just sent some fixes for this. Could you try again, please? 🙇

@Doomsdayrs
Copy link
Author

So?

@g0dkar
Copy link
Owner

g0dkar commented Feb 6, 2023

Hey everyone, sorry for taking so long to take care of this one. Life got quite hectic in the past 6 months or so.

Could you confirm you can build the project now @Doomsdayrs and @shalva97? Thanks!

@g0dkar g0dkar closed this Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants