Austin Harris

@kierandesmond Does that solution allow the link to survive the app install process? I could be wrong on this but I'm pretty sure the firebase sdk's have special logic for...

This appears to happen when you have defined roles for each lambda function separately. If the same permissions are placed in the default role, and I do not define explicit...

This seems to be related to an undefined stack output showing up. The stack output for the first stream binding gets stored in the stack as undefined, so it binds...

```await MyModel.destroyAsync('Id-123', 'Id-123', { expected: { Id: { Exists: true } } })``` generates ```{ TableName: 'myTable', Key: { Id: 'Id-123', EntityId: 'Id-123' }, ExpressionAttributeNames: { '#EntityId': 'EntityId', '#Id': 'Id'...

A valid workaround for now is to pass Expected in to the params: ``` await MyModel.destroyAsync('Id-123', 'Id-123', { Expected: { Id: { Value:'Id-123' }, EntityId: { Value: 'Id-123' } }...

@rlemasquerier @mikehardy It's entirely possible I missed this due to my inexperience contributing to native libraries and an over-reliance on the unit tests telling me everything was ok 😅. Probably...

@HyperBrain `pnpm ls` appears to return a single level of the tree. It's not totally clear to me how the plugin or pnpm work together yet, but I gave it...

@HyperBrain It appears to be an npm tree. The docs for [pnpm-list](https://github.com/pnpm/pnpm-list) back this up: `Returns a string output similar to the npm ls but for pnpm.` I tried it...

@mledom sorry I've left this for so long, I got tied up with other projects and am no longer using serverless. Per @HyperBrain's comment it uses the same tree structure...

This issue is effectively blocking people who use react-native-firebase from upgrading to >= rnfb@15 and subsequently >= [email protected]. As the firebase-ios-sdk is not planning to remove use_frameworks, the only way...