Mohamed Yassin

@tommybananas Sorry for the late reply, but scopes won't actually fix the issue, I tried, the same endpoint always. @wroberts Looks fine!

I've worked around this by decoding the parameter myself ``` screenName: { path: 'screenName/:id', parse: { id: (id: string) => decodeURIComponent(id), }, }, ```

Removing the spaces is definitely going to fix it, it is better though to replace the `HEADER_SEARCH_PATHS` with ``` HEADER_SEARCH_PATHS = ( "$(inherited)", ); ``` then run `pod install` in...

@okainov the page doesn't have any captchas anymore

Hi @chrisbonifacio, I'm using `amplify v12.12.0` and this is how the model looks like in the schema: ```graphql type User @model @auth( rules: [ { allow: owner operations: [read, update,...

Hi @cwomack, yeah sure, here you go: ```json { "dependencies": { "@aws-amplify/react-native": "1.1.1", "@aws-amplify/rtn-web-browser": "1.0.30", "@azure/core-asynciterator-polyfill": "1.0.2", "@georstat/react-native-image-cache": "2.8.0", "@nozbe/watermelondb": "0.27.1", "@react-native-async-storage/async-storage": "1.21.0", "@react-native-clipboard/clipboard": "1.13.2", "@react-native-community/netinfo": "9.4.1", "@react-native-firebase/app": "18.7.1", "@react-native-firebase/messaging":...

Hello @ashika112, I didn't try since quite a while, we're using 12.11.x still

I've adjusted the regex a bit to also include `t` methods where you use variables, ```regex /t\(\s*["'`]?([\s\S]+?)["'`]?\s*(?:\)|,)|i18nKey="([\s\S]+?)"/gi ``` Now this would be matched correctly as well ```ts t(`translation.key`, { variable:...

It was failing for me on Node v21 downgrading to Node v20 fixed it

Hello @anivar, does the watermelonDBAdapter support custom primary keys? That is actually a current limitation in the `@aws-amplify/datastore-storage-adapter/SQLiteAdapter`