Appauth-android: New release request

[axnd]

I just noticed that in master the supportLibVersion is > 26 but in 0.7.0 it's still 25, any chance we can get a tag and release sometime soon so that I (and others) can start targeting v26?

[Eagle9Eye]

Any word on this?

[barbeau]

I'd like to voice support for a new release w/ v26 of the support library as well. We (OneBusAway) are using the EmbeddedSocial SDK which has a dependency on this library, and we have to use v26 of the support library in our app. Android Studio 3.0 and higher flags this as an error in build.gradle.

cc @acrown-msft

[sunenielsen]

Any plans for a new release? It's been half a year now.

[iainmcgin]

I'm working out contributor license agreement issues with my new employer; hopefully that will happen soon, and then I can take control of this project again.

[jfitz1]

+1 on new release

[CodyDunlap]

+1 on new release. There are several major issues that have been fixed but still waiting on a release.

[thibaultmeyer]

@iainmcgin Is it possible to have a new release. Important PR has been merged since august 2017 (ie: #309)

[pvegh]

No answer. Project is dead.

[ve7jtb]

I just talked to Ian yesterday. The project is defiantly not dead.

I will work with him to sort out any issue caused by his change of employment.
I know he is planning on continuing.

John B.

[CodyDunlap]

Any update on this? We've been waiting for a new release with important updates for a while now and still no word.

[CodyDunlap]

@ve7jtb Any update on this? I've seen activity here and there from Ian but no response on this. I know there is activity but this project feels dead when we can't get any updates released for over a year.

[iainmcgin]

The project isn't dead. We don't commit to any release schedule, and as far as I'm aware none of the patches we have taken in for the last year fix any significant bugs or issues, so that seems overstated.

Regardless, I'll get a new release out this week.

[iainmcgin]

0.7.1 has been tagged and pushed to jcenter. I'm going to add instructions to the README on how to use jitpack to reference the library at any commit you like, to make it clear to everyone that we're not blocking anyone by not cutting "official" releases on some regular cadence.

[CodyDunlap]

Thanks Ian! The #309 issue that I fixed was causing users to get kicked out of apps frequently because the library would return an AuthorizationException any time multiple requests that need a token refresh were fired in async. I'll be sure to use jitpack in the future if I'm waiting on a feature like this though. Thanks again!