-
```
What steps will reproduce the problem?
1. Create a UTF-8 encoded AndroidManifest.xml.
2. Setup Maven build to use UTF-8 for all files.
3. Add a comment to a Manifest file containing characters not…
-
```
In the latest version 3.6.0. Annotation Processing stopped working for library
projects. I'm using androidannotations that generates a whole lot of classes at
compile time. If the same project i…
-
```
What steps will reproduce the problem?
1. Create a UTF-8 encoded AndroidManifest.xml.
2. Setup Maven build to use UTF-8 for all files.
3. Add a comment to a Manifest file containing characters not…
-
Hi there,
I'm using AndroidAnnotations 3.3.1.
Recently I encountered a use case where I wanted to display or hide the options menu based on the incoming Intent action.
More specifically I'm using …
-
```
What steps will reproduce the problem?
1. Use AndroidAnnotations with GSON as Converter. (Basically Spring REST)
2. Run Proguard with the config I'm attaching.
3. Run App.
What is the expected ou…
-
```
What steps will reproduce the problem?
1. Use AndroidAnnotations with GSON as Converter. (Basically Spring REST)
2. Run Proguard with the config I'm attaching.
3. Run App.
What is the expected ou…
-
```
What steps will reproduce the problem?
1. annotation "@ReportsCrashes(formKey = "", mode =
ReportingInteractionMode.TOAST, resToastText = R.string.unexpected_error)" does
not compile with androi…
-
```
What steps will reproduce the problem?
1. Use AndroidAnnotations with GSON as Converter. (Basically Spring REST)
2. Run Proguard with the config I'm attaching.
3. Run App.
What is the expected ou…
-
I don't know if this is an issue with Dagger 2.0 or Android AppCompat....
We are using android.support.v4.app.DialogFragment and Dagger 2. When switching from appcompat-v7:22.1.0 to appcompat-v7:22.…
-
```
What steps will reproduce the problem?
1. My build was working fine with AndroidAnnotations, Dagger, and a slightly
modified version of CleanAndroidCode project that adds additional entry point
…