No static method loadLibrary in class

[tyronen]

(Hi @passy, if you're reading this, good to 'see' you again.)

This was previously reported in #10. I get https://pastebin.com/R5zfJtNn when starting up our app. Occurs with 0.5.0 and also with 0.4.1, but not with 0.3.0. Rebooting the Mac, as advised in that issue, did not help. We didn't attempt running with Windows.

Repro steps:

Our app had been running fine with SoLoader 0.4.1 and Fresco 1.9.0. We were doing a lazy-init of SoLoader; it is initialized by Fresco, and we didn't initialize Fresco until loading the first view with an image.

Lately we tried to add Sonar to the app. This requires calling SoLoader.init directly in the Application.onCreate method. This craps out.

The workaround is to downgrade to 0.3.0, but hopefully this can be fixed long term.

[cristianonescu]

@tyronen did you figured this out? I'm also having this error

[passy]

Hey! Sorry for the slow response. I'm not entirely sure where this would come from. I don't have a good repro for this, so the best thing I can offer right now is to just publish another release based off master and see if that does anything.

[passy]

I've put up a 0.5.1 which should trickle through the Maven Central release process within the next hour or so. It would be great to know if that makes any difference at all for you two.

[michalgr]

Hi @tyronen :)

The error message complains about lack of void loadLibrary(String) method. Well, it is indeed gone as of 9169960#diff-be862dcc6d9e7bd0e7fe754df40a9bca. Seems that your app includes libraries that were compiled against different versions of SoLoader interface.

[passy]

Ahh, thanks for the explanation, @michalgr!

[michalgr]

The interface changed between 4.1 and 5.0. Fresco pulls in SoLoader 5.0 and Sonar pulls in 4.1 and we have a disaster.

Valuable lesson for me: do not let public API to change. I am sorry for that.

@passy: can we update Sonar deps and organize a new release ?

[passy]

@michalgr Yes, I'll do that now.

[Gadigg]

Just started having this problem too a few hours ago..
Can't believe I caught this thread live

@passy after your PR get's approved it should be resolved after a gradle sync?

[passy]

I'll need to push out a new release too, but that should take care of it.

On Tue, 17 Jul 2018, 17:38 Gadigg, ***@***.***> wrote: Just started having this problem too a few hours ago.. Can't believe I caught this thread live @passy <https://github.com/passy> after your PR get's approved it should be resolved after a gradle sync? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAmsqftXLiDEvBQypKEMrYpWe89l-fKks5uHhL4gaJpZM4VFZWb> .

-- timezone: eu/london | utc+1 @passy

[cristianonescu]

@passy any ideea how soon will this happen? When will we be able to pass this? 😭

[passy]

@cristianonescu The Sonar release? I can do that tomorrow.

[patrickkempff]

Related react-native issue: facebook/react-native#20242

[passy]

New Sonar release is out as 0.6.12.

[passy]

Still working on the long tail of this. Released 1.9.0 of Yoga today which uses the new version of SoLoader will release 0.19.0 of Litho tomorrow which will have both SoLoader >= 0.5.0 and Yoga 1.9.0 as dependency.

[gengjiawen]

0.5.1 still has this issue.

[passy]

@gengjiawen The SoLoader package is fine. You have an old dependency that is linked against an older version of SoLoader and are mixing it with a > 0.5.1. I'm closing this issue now because I've updated all the packages I have any control over.

[gengjiawen]

@passy Nope, You can see facebook/react-native#20325.