Parse4cn1 conflicts with codename one when using facebook sdk on Android

[mariobaron29]

hey sidiabale, first of all thanks a million for getting this to work as a viable alternative for using parse server on CN1, especially for the push notifications functionality.

As you may have guessed, I'm implementing push notifications on my CN1 app via parse4cn1 but I'm getting a build error when using it alongside the Facebook SDK. As far as I know, this is due to Facebook and Parse4cn1 using the bolts library and therefore getting added twice.

Shai mentioned on the Codename One forums building the parse4cn1 without the bolts library as a possible solution to this problem but frankly I'm not skilled at native app development either for Android or iOS, can you please take a look at this?

Thanks before hand.

[sidiabale]

Hey! Great to hear you're trying out parse4cn1. The issue you faced is a known one and the suggestion to compile parse4cn1 without bolts is not that simple. This is because bolts is 'inherited' from the parse native SDK and I'm not sure how far the dependencies go. Technically it would be possible to fork the Parse iOS SDK repo and create a version that addresses this problem but that's an involved task which I unfortunately cannot work on right now. Can you share the link to the forum post you mentioned?

…

On Wed, Sep 20, 2017 at 11:55 PM, mariobaron29 ***@***.***> wrote: hey sidiabale, first of all thanks a million for getting this to work as a viable alternative for using parse server on CN1, especially for the push notifications functionality. As you may have guessed, I'm implementing push notifications on my CN1 app via parse4cn1 but I'm getting a build error when using it alongside the Facebook SDK. As far as I know, this is due to Facebook and Parse4cn1 using the bolts library and therefore getting added twice. Shai mentioned on the Codename One forums building the parse4cn1 without the bolts library as a possible solution to this problem but frankly I'm not skilled at native app development either for Android or iOS, can you please take a look at this? Thanks before hand. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#32>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABJAdHFiIvo4rNPI2TfCmn4QEmTgpEeeks5skYm2gaJpZM4Pehw_> .

[mariobaron29]

Hey man, the link to the mentioned post in the CN1 forums is the following link

I'm trying out a different approach at this, I got the sources to the parse and the bolts library and I'm simply renaming the bolts package so it doesn't get conflicted with the facebook one, I know it's probably not the best approach but I'm needing to solve this problem urgently. I think I'm probably close to cracking it but I'm working with the Java 8 jdk and don't know how to build the parse and bolts libraries with the Java 7 jdk which is causing a problem when building the app for Android right now.

Am I on the right track? Thanks for your help.

parse4cn1 error log.txt

[mariobaron29]

Hey man I've managed to come up with a manual solution for this problem I'll walk you through my solution and let's see if you can help me automate the solution.

1. I downloaded your parse4cn1.cn1lib file and opened it with winrar
2. I accessed the nativeand.zip file and removed the bolts-tasks-1.4.0.jar file
3. I took the parse4cn1.cn1lib file and put it in my lib folder on my codename one project and hit the refresh libs option.
4. Compiled the app for Android
5. Since I have a Pro account, I downloaded the project's native sources and opened the project with Android Studio.
6. I added the bolts-tasks-1.4.0.jar back into the libs folder of the Android Project.
7. I replaced the following dependency:
   compile 'com.facebook.android:facebook-android-sdk:4.7.0'
   on the build.gradle file with the following:
   compile ('com.facebook.android:facebook-android-sdk:4.7.0'){ exclude module: 'bolts-android' }
8. Clean and Rebuild the project and it's now running on my Android Device

I know this is a rather manual way of doing it but it works! Maybe with your greater knowledge on cn1Libs and if we talk to the Codename one team we could probably get this to be done through a build hint or something like that.

Please tell me what you think about this solution and if we can make this work to be integrated in a more seamless manner. Thanks!

[sidiabale]

Hey, glad to hear you found a workaround and sorry for the late response (neck-deep in other stuff at the moment). Your approach sounds indeed like something that probably could be tackled with a build hint. Ask Shai and let's see what he says.

…

On Thu, Sep 28, 2017 at 6:41 PM, mariobaron29 ***@***.***> wrote: Hey man I've managed to come up with a manual solution for this problem I'll walk you through my solution and let's see if you can help me automate the solution. 1. I downloaded your parse4cn1.cn1lib file and opened it with winrar 2. I accessed the nativeand.zip file and removed the bolts-tasks-1.4.0.jar file 3. I took the parse4cn1.cn1lib file and put it in my lib folder on my codename one project and hit the refresh libs option. 4. Compiled the app for Android 5. Since I have a Pro account, I downloaded the project's native sources and opened the project with Android Studio. 6. I added the bolts-tasks-1.4.0.jar back into the libs folder of the Android Project. 7. I replaced the following dependency: compile 'com.facebook.android:facebook-android-sdk:4.7.0' on the build.gradle file with the following: compile ('com.facebook.android:facebook-android-sdk:4.7.0'){ exclude module: 'bolts-android' } 8. Clean and Rebuild the project and it's now running on my Android Device I know this is a rather manual way of doing it but it works! Maybe with your greater knowledge on cn1Libs and if we talk to the Codename one team we could probably get this to be done through a build hint or something like that. Please tell me what you think about this solution and if we can make this work to be integrated in a more seamless manner. Thanks! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#32 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABJAdFbty0r_vkBMBYDQJE0nypJYhimQks5sm8w7gaJpZM4Pehw_> .