[runningcode]

📜 Description

Moves the JetBrains @Nullable from the element type to the array on six public methods that return a nullable array:

• Attachment.getBytes()
• Device.getArchs()
• Spring.getActiveProfiles()
• ContextUtils.getSplitNames()
• JsonSerializationUtils.bytesFrom(...)
• QueueFile.peek()

💡 Motivation and Context

JetBrains @Nullable is a TYPE_USE annotation, so @Nullable byte[] marks the element type, not the array. Kotlin saw these returns as ByteArray and Array<String>, although they can return null. With byte @Nullable [] Kotlin sees ByteArray? and Array<String>?.

Follow-up to the review on #6497, which fixed the same thing on ViewHierarchyEventProcessor.snapshotViewHierarchyAsData. The ScreenshotUtils returns use androidx.annotation.Nullable, a declaration annotation that Kotlin already reads as a nullable return, so they stay as they are.

💚 How did you test it?

A Kotlin assignment of each kind of return to a non-null type now fails to compile. The Kotlin tests of the modules that call these methods still compile, and their unit tests pass.

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

Kotlin code that uses these returns as non-null, for example attachment.bytes.size, no longer compiles until it handles null.

🤖 Generated with Claude Code

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.63.0 (1)	release

⚙️ sentry-android Build Distribution Settings