Skip to content

Conversation

@mdydek
Copy link
Contributor

@mdydek mdydek commented Jan 12, 2026

Closes RNAA-397, RNAA-370

⚠️ Breaking changes ⚠️

  • new android recording notification

Introduced changes

Checklist

  • Linked relevant issue
  • Updated relevant documentation
  • Added/Conducted relevant tests
  • Performed self-review of the code
  • Updated Web Audio API coverage
  • Added support for web

@mdydek mdydek added the feature New feature label Jan 13, 2026
@mdydek mdydek marked this pull request as ready for review January 13, 2026 14:35
Unregister the notification from the system. Must call `register()` again to use.
| Error type | Description|
| :--------: | :---------- |
| `NotSupportedError` | NativeAudioAPIModule is not available |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not think that we want to add this type of error to this section of docs

};
}, []);

const setNotification = (paused: boolean) => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it possible to set icons once and than only change contentText?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, we could split the notification setup into config and state options

}

if (!NativeAudioAPIModule) {
throw new Error('NativeAudioAPIModule is not available');
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it should be sth like AudioAPIError

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't there all errors that are not directly connected with audio api implementation, be like that then?
f.e. throw new Error('Unsupported input type or failed to decode audio'); in decoder

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's right

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can add some section about that kind of errors to docs


if (!NativeAudioAPIModule) {
throw new Error('NativeAudioAPIModule is not available');
throw new NotSupportedError('NativeAudioAPIModule is not available');
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
throw new NotSupportedError('NativeAudioAPIModule is not available');
throw new AudioAPIError('NativeAudioAPIModule is not available');

Copy link
Member

@michalsek michalsek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good, but lets talk a bit what to do about reverts that not necessarily we would like to be reverted. We can create followup tasks if they are not critical to "revert the revertion" later, for important parts it would be best to bring them back before merge'ing

@mdydek mdydek self-assigned this Jan 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants