Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
This repository was archived by the owner on Feb 26, 2023. It is now read-only.

Change "report an issue" message #613

Copy link
Copy link
@DayS

Description

@DayS
Issue body actions

Currently if AA crashes during code generation, we print the following output :

Please report an issue on AndroidAnnotations, with the following content : [Insert stack trace here]

We have lots of issues with only this message. I suppose people think this is enough to debug their code, or just too busy to add more details. As we're also very busy, I think we should inject more information in this message like :

  • the version of AA
  • the context (1~3 lines around the line of the crash)
  • the reproducibility of the crash
  • the stacktrace

We could have something like that :

Unexpected error. Please report an issue on AndroidAnnotations for version 2.7.1, with the following content and tell us if you can reproduce it or not : java.lang.NullPointerException on
"@extra(resName="unknownExtra") String username;" with stacktrace
[Insert stack trace here]

Reactions are currently unavailable

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.