4

The @JavascriptInterface annotation works on api 17 and above. For my project the annotation cannot be found as my target api is set to 13:

my project build target

and in my manifest the min sdk is 11:

 <uses-sdk
    android:minSdkVersion="11"
    android:targetSdkVersion="18" />

Why do I have to go into the project build target (e.g., Project > Properties > Android in Eclipse) and change it to API 17+ as a resolution. Now I have to build against that SDK when all I really want to do is ignore the annotation on anything below API 17. Is there anyway I can do that? I dont like the idea of building against api 17 and then later finding out I have code that wont run on prior releases. My goal is to ensure my app can run on api 13 to 18. If commonsWare is around maybe he can suggest something I'm missing...

MMG
  • 3,226
  • 5
  • 16
  • 43
j2emanue
  • 60,549
  • 65
  • 286
  • 456
  • 1
    JavaScript bridges are a security issue on API < 17. See http://50.56.33.56/blog/?p=314 for detailed information and a way to do it securely on API < 17. – domen Oct 30 '13 at 15:25
  • @domen Technically it seems to be a security issue on all versions above 2.3, that are done without the `@JavascriptInterface` - except for 4.2+, when compiled with the `@JavascriptInterface` directive. See http://stackoverflow.com/questions/6415882/android-javascriptinterface-security#comment27242971_18510063 – NoBugs Jan 05 '14 at 09:25
  • OK I have to admit I'm currently just a tad beyond "surprised" and "impressed" that the IP addres above *still works* just under 10 years later. The path didn't though; I got an article listing instead. But I found the article in 15 seconds! And clicking the link fixed the domain too: https://d3adend.org/blog/posts/abusing-webview-javascript-bridges/ – i336_ Oct 06 '22 at 16:45

1 Answers1

1

For my project the annotation cannot be found as my target api is set to 13:

Then fix that, or set your android:targetSdkVersion low enough that you do not need @JavascriptInterface.

Why do i have to go into the project build target (e.g., Project > Properties > Android in Eclipse) and change it to API 17+ as a resolution.

Because @JavascriptInterface does not exist prior to API Level 17, just as DisplayManager does not exist prior to API Level 17.

Now i have to build against that SDK when all i really want to do is ignore the annotation on anything below API 17.

Since your build target does not affect anything other than what classes, methods, annotations, etc. are available to you, I fail to see the concern.

I dont like the idea of building against api 17 and then later finding out i have code that wont run on prior releases.

Lint has been reporting API level violations for well over a year. Just make sure your android:minSdkVersion is set properly.

After all, you were already relying upon this, as your android:minSdkVersion is set to 11 and your build target is presently set to 13. That means that you are counting Lint to report where you are using API Level 12 and API Level 13 APIs so that you can handle them properly. All you are doing by raising the build target is raising the number of things that you are relying upon Lint for.

CommonsWare
  • 986,068
  • 189
  • 2,389
  • 2,491