How to obtain token for Reaper? | Sentry Community | Page 1

digital karma Dec 23, 2025, 5:20 PM

#

hi 👋 . I read An open-source SDK for finding dead code article and tried to integrate Reaper in my Android app. But I'm getting

Unexpected code Response{protocol=h2, code=403, message=, url=https://api.emergetools.com/upload}

when building the app. I'm guessing that the lack of EMERGE_API_TOKEN is the problem. But I can't find any up to date information on how to obtain one. Do I still need Emerge account/subscription to use this tool, even though SDKs and backend are open source now?

Product Blog • Sentry

Reaper - An open-source SDK for finding dead code

Writing code is easier than ever. We want to make deleting code just as easy – introducing Reaper for iOS and Android. Reaper was an Emerge Tools product that h...

digital karma Dec 23, 2025, 6:43 PM

#

I was thinking that, as long as I use my own backend, I don't need to use Emerge Gradle Plugin but without it the app logs in runtime

Reaper is not enabled, ensure this variant is specified in the reaper.enabledVariants list in the Emerge gradle plugin configuration block. See https://docs.emergetools.com/docs/reaper-setup-android#configure-the-sdk.

so I guess I need it?

#

Actually, reading how it works under the hood, it makes sense that a build-time plugin is necessary 🙂

digital karma Jan 6, 2026, 1:31 PM

#

hello folks, a friendly ping: is it possible to use Reaper these days if I'm not registered at Emerge Tools?

idle cobalt Jan 7, 2026, 9:55 AM

#

digital karma hi 👋 . I read [An open-source SDK for finding dead code](https://blog.sentry.io...

Hey! Sorry @digital karma this got a bit lost over the holidays XD. Yes it is possible to use however we don't offer a 'service' backend for Reaper anymore. If you want to use it now you have to stand up your own backend to receive and process the reports. On the client side that looks like setting your custom URL in the manifest as mentioned here: https://blog.sentry.io/an-open-source-sdk-for-finding-dead-code/#reaper-for-android-4

#

On the backend side a very minimal backend is available here as a starting point: https://github.com/EmergeTools/oss-reaper

#

Let me know if that helps and if you have any further questions!

digital karma Jan 7, 2026, 1:50 PM

#

No worries, completely understandable. Thank you for the reply @idle cobalt ! 🙂

It's great that you offer it, and I'm completely fine with hosting our own backend for Reaper. But still, the Reaper Gradle Plugin doesn't work without EMERGE_API_TOKEN and when I provide a dummy value, I'm getting 403 (as in the first message).

What value can I provide there for Reaper Gradle Plugin to work?

idle cobalt Jan 7, 2026, 2:04 PM

#

Ah I see! Hmm that's werid :/ Does the message still show same URL: Unexpected code Response{protocol=h2, code=403, message=, url=https://api.emergetools.com/upload}? I would have expected it to say something different if the override is being picked up.

#

One thing to double check is which version of the Emerge Gradle Plugin and Reaper library you are on. https://github.com/EmergeTools/emerge-android/releases

#

Hmm actually it looks like we don't have an official release of the Repaer library with the override in yet.

#

Which would explain the issues you are having. Right now you can use emergeReaper = "1.0.1-SNAPSHOT". I'll try and sort out a 1.0.2 release shortly.

digital karma Jan 7, 2026, 6:49 PM

#

Thank you for checking! I'll test the 1.0.1-SNAPSHOT and reply here later this week 👍

digital karma Jan 8, 2026, 10:24 AM

#

👋

Which would explain the issues you are having. Right now you can use emergeReaper = "1.0.1-SNAPSHOT". I'll try and sort out a 1.0.2 release shortly.

I see you mean the runtime library - I understand and updated it but it didn't help. I think the problem is before the app launches - at the time of actual build time.

Assuming I have a simple configuration like this

plugins {
    id("com.emergetools.android") version "4.4.0"
}

emerge {
    reaper {
        enabledVariants = ["myVariant"]
        publishableApiKey = "key"
    }
}

when I execute

./gradlew emergeReaperPreflightMyVariant

I'm getting

╔═════════════════════════════════════╗
║ Reaper preflight check failed (3/4) ║
╠═════════════════════════════════════╝
╠═ ❌ Emerge API token set
╠═ ✅ enabled for variant: wordpressVanillaRelease
╠═ ✅ publishableApiKey set
╚═ ✅ Runtime Library added

I think in the current form, the Reaper Gradle Plugin still needs the Emerge API token. So this circles back to my original question: is it possible to obtain the token somehow?

digital karma Jan 8, 2026, 10:41 AM

#

updated it but it didn't help
a sorry, I didn't really tested the snapshot, I'm actually getting Could not find com.emergetools.reaper:reaper:1.0.1-SNAPSHOT. during the build

#

I mean, I think it all comes down to apiToken beeing required here: https://github.com/EmergeTools/emerge-android/blob/1ab2ee2b63cd3ae62b9e1a5f5597c98227a8605e/gradle-plugin/plugin/src/main/kotlin/com/emergetools/android/gradle/EmergePluginExtension.kt#L24-L30 and it's not a token to my backend, but to Emerge Tools API if I'm reading it right

#How to obtain token for Reaper?