Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- akenaton September 2015
- hudson_m4000 September 2015
3.0b6 errors
Like a few other users, I am struggling to get working with 3.0b6 AndroidMode. I have everything installed as far as I can tell using the embedded sdk downloader etc., and I can do an export of my sketch which loads fine into AIDE on my phone where I can then create an apk.
But, I used to be able to 'run on device' with Processing up until having to get a new PC this and re-install everything, and now I get some weird errors. The first is when importing an android library class eg:
import android.view.MotionEvent;
which gives the error message:
** Only a type can be imported. android.view.MotionEvent resolves to a package**
And the second is when I run on device where the console says:
**Using latest Build Tools: 23.0.1 [echo] Resolving Build Target for androidTest...
BUILD FAILED C:\Users\Mark\Documents\Processing\modes\AndroidMode\sdk\tools\ant\build.xml:538: Unable to resolve project target 'android-22'**
I know others seem to have similar issues... any solutions though?!
Mark
Answers
OK I have fixed the 2nd problem by getting the right API's installed..
@hudson_m400 put your import statements and some code
Both issues are gone now ..
After all my fiddling with different APKs and the manifest issue in my other thread, it all seems to be fixed.