Skip to content

refactored to work on Android N #418

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

Closed
wants to merge 3 commits into from
Closed

refactored to work on Android N #418

wants to merge 3 commits into from

Conversation

gulo-gulo
Copy link

No description provided.

@facebook-github-bot
Copy link

By analyzing the blame information on this pull request, we identified @grantland, @wangmengyan95 and @Allsimon to be potential reviewers.

@facebook-github-bot
Copy link

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at [email protected]. Thanks!

@facebook-github-bot
Copy link

@sudochownrwhoami updated the pull request.

@gulo-gulo
Copy link
Author

Hi facebook-github-bot,

I signed up. That aside:

I'm attempting to provide a working version of the Parse Android SDK specifically for the Android N Developer Preview

The automated build failed because of the gradle version I am using that is apparently required for the Android N dev preview builds

@facebook-github-bot
Copy link

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@facebook-github-bot
Copy link

@sudochownrwhoami updated the pull request.

@grantland
Copy link
Contributor

It's awesome that you've looked into this! Is there a problem using the SDK on Android N or is this allowing the SDK to compile with Android N?

We currently have an issue for getting the SDK to compile under Android M as it relies on APIs removed in M, but it works on M without any changes: #189

It seems like you've done the basic work outlined in that issue, however, your work will also break compatibility with < android-11 since Notification.Builder requires android-11 and I don't think we're ready to remove support for < android-11.

Additionally, you can update .travis.yml to get the tests passing.

@facebook-github-bot
Copy link

@sudochownrwhoami updated the pull request.

@grantland
Copy link
Contributor

Still waiting for working Travis-CI config

@ghost ghost added the CLA Signed label Jul 12, 2016
compile 'com.parse.bolts:bolts-tasks:1.4.0'

compile 'org.apache.httpcomponents:httpclient-android:4.3.5.1'
Copy link
Member

Choose a reason for hiding this comment

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

This is unnecessary since you already have useLibrary 'org.apache.http.legacy'

Copy link
Contributor

Choose a reason for hiding this comment

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

delete line

@Jawnnypoo
Copy link
Member

This should be updated to use non-beta versions of things like the compile SDK, build tools, etc.

@@ -9,20 +9,22 @@ version = '1.13.1-SNAPSHOT'
buildscript {
repositories {
mavenCentral()
Copy link
Contributor

Choose a reason for hiding this comment

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

you can kill this line, maven is redundant

@@ -204,6 +214,6 @@ task jacocoTestReport(type:JacocoReport, dependsOn: "testDebugUnitTest") {

//region Coveralls

coveralls.jacocoReportPath = "${buildDir}/reports/jacoco/jacocoTestReport/jacocoTestReport.xml"
Copy link
Contributor

Choose a reason for hiding this comment

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

can you add this back in?

compile 'com.parse.bolts:bolts-tasks:1.4.0'

compile 'org.apache.httpcomponents:httpclient-android:4.3.5.1'
provided 'com.squareup.okhttp:okhttp:2.4.0'
Copy link
Contributor

Choose a reason for hiding this comment

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

these need to go to okhttp3

@Jawnnypoo
Copy link
Member

@rogerhu Would you be willing to accept #554 instead? Reasoning: all of the work here is included in that PR and is ready to merge, and reducing down to just the OkHttp client reduces the amount of support needed for the project.

@rogerhu
Copy link
Contributor

rogerhu commented Mar 8, 2017

I think we need to get OkHttp3 stabilized with some of the more minor issues (i.e. v1.13.2 or v1.13.3) first -- waiting to hear back about the process to push to Sonatype/Maven, or if it's already automated if I push/tag a release.

But let me look at that other PR..

@rogerhu
Copy link
Contributor

rogerhu commented Mar 8, 2017

Closing in lieu of #554

@rogerhu rogerhu closed this Mar 8, 2017
@Jawnnypoo
Copy link
Member

Sounds good. If nothing else, the library could be moved to a JitPack distribution since that requires no authentication to distribute so long as you can make tags in GitHub.

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.

6 participants