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

Cannot build against Amazon Fire/FireTV API #259

Open
y3ddet opened this issue Jun 6, 2014 · 2 comments
Open

Cannot build against Amazon Fire/FireTV API #259

y3ddet opened this issue Jun 6, 2014 · 2 comments
Assignees
Labels
Milestone

Comments

@y3ddet
Copy link

y3ddet commented Jun 6, 2014

Line 132 of src/org/mythtv/client/ui/preferences/MythPreferenceActivity.java causes a compiler error due to the Build.VERSION_CODES.KITKAT while Amazon headers define only up to JELLY_BEAN.

Further the isValidFragment() routine is not defined in the Fire SDK based in 4.4.2.

Is there a way to correctly control this fragment such that it wont conflict with the KITKAT build for mainline Android builders?

@billmeek billmeek added the bug label Jun 8, 2014
@billmeek billmeek modified the milestones: 1.30.0, 1.20.7 Jun 8, 2014
@billmeek
Copy link
Contributor

billmeek commented Jun 8, 2014

Thanks for the report (and the comment on the Beta G+ list.) Set to Bug/1.20.7. http://securityintelligence.com/new-vulnerability-android-framework-fragment-injection/

@y3ddet
Copy link
Author

y3ddet commented Jun 8, 2014

[EDIT] Ignore this, it was due to a maven/ADK/Eclipse config. I still cannot generate through the Eclipse tools, but command line invocation of the "package" goal works.

When commented out, and Android 4.2.2 or the Amazon Fire API selected, compilation works, however no binaries appear to be merged into the resulting APK file. I can install it through ADB, but of course it fails to find the main class object identified in the manifest to execute. I can find the Java .class files in the Eclipse navigator, so javac appears to be working correctly, so the issue must be somewhere in either the Maven target, or the Eclipse configuration that causes the resulting .class files to be added to the jar/apk file. Any suggestions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants