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

External build files / force resync #18

Open
usernotnull opened this issue Feb 24, 2018 · 10 comments
Open

External build files / force resync #18

usernotnull opened this issue Feb 24, 2018 · 10 comments

Comments

@usernotnull
Copy link

The moment i implemented this library, I always keep getting the message:

External build files have changed since last project sync. A project sync may be necessary for the IDE to work properly.

I pressed "Sync Now" but after each resync, the message comes back. Same if i do a project Rebuilt, the message doesn't go away.

Any idea how to solve this? thanks

@krokyze
Copy link

krokyze commented Feb 25, 2018

I'm having the same issue.

@jrcacd
Copy link

jrcacd commented Mar 6, 2018

I have the same issue.

@palorotolo
Copy link

+1

2 similar comments
@itcherry
Copy link

+1

@demogorgorn
Copy link

+1

@ValeryP
Copy link

ValeryP commented Apr 9, 2018

I have the same issue.

@MEiDIK BTW, if I run clean I'm getting the next error:

More than one externalNativeBuild path specified

I use ndkBuild for the project (not cmake that Cipher plugin uses).

externalNativeBuild {
    ndkBuild {
      path 'src/main/jni/Android.mk'
    }
  }

If I comment the code block above projects syncs fine and builds the .so lib correctly.

@linisme
Copy link
Owner

linisme commented Apr 9, 2018

@ValeryP cipher.so does not support ndkbuild

@demogorgorn
Copy link

Have the same issue. I have noticed that on computer with SSD drive there is no that problem, but on computer with HDD - there is problem.

For today I stopped using this lib because of this problem :(

@rizmaulana
Copy link

+1

@rizmaulana
Copy link

Have the same issue. I have noticed that on computer with SSD drive there is no that problem, but on computer with HDD - there is problem.

For today I stopped using this lib because of this problem :(

I already use SSD and still get this error message

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

No branches or pull requests

9 participants