# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand. overlay: 1.0.0 info: title: API Evangelist conversational phrasing for BugSnag - Upload Android API version: 1.0.0 extends: openapi/bugsnag-android-api-openapi.yml actions: - target: $.info update: x-apievangelist-phrasing: method: generated generated: '2026-09-26' generator: build-phrasing.py label: Generated by API Evangelist operations: 2 - target: $.paths['/ndk-symbol'].post update: x-apievangelist-phrasing: intent: Upload Android NDK shared object symbols effect: write questions: - How do I get readable native stack traces for my Android NDK crashes? - Can I upload a stripped .so file so native frames show function names? - Which version code should the shared object symbol upload be tied to? instructions: - text: Upload the NDK shared object file {soFile} for app {appId}. slots: soFile: requestBody.soFile appId: requestBody.appId - text: Upload native symbols {soFile} for Android version code {versionCode} and overwrite any existing upload. slots: soFile: requestBody.soFile versionCode: requestBody.versionCode method: generated generated: '2026-09-26' - target: $.paths['/proguard'].post update: x-apievangelist-phrasing: intent: Upload an Android ProGuard mapping file effect: write questions: - How do I deobfuscate Java stack traces from a minified Android build? - Can I send my R8 or ProGuard mapping.txt to BugSnag for a specific version code? - What app ID and version code does a mapping file upload need? instructions: - text: Upload ProGuard mapping {proguard} for app {appId} version code {versionCode}. slots: proguard: requestBody.proguard appId: requestBody.appId versionCode: requestBody.versionCode - text: Send the R8 mapping file {proguard} for build UUID {buildUUID}. slots: proguard: requestBody.proguard buildUUID: requestBody.buildUUID method: generated generated: '2026-09-26'