Daryl Beattie

This issue still exists, FYI.

Hi Abdallah, Thanks for responding about my issue. That's great, yes -- and I did see that article already and read it. :) But the big question after I read...

And another big question.... I just logged this bug: https://github.com/aws-amplify/amplify-js/issues/11785 Will this new logger make that bug completely obsolete? (I thought you were replying about my new bug, but it...

Wow, uh… honestly you made my day. 🙂 Thank you!!! - Daryl. On Thu, Aug 10, 2023 at 11:36 PM Abdallah Shaban ***@***.***> wrote: > We will fix this bug...

Manually removing the layer from the `amplify-meta.json` worked. So the bug is that it is placed there in the first place.

Hi @ykethan , no it doesn't list it there when I do `amplify status`. It was _only_ there when I tried to do the amplify-push after creating the new env....

I have temporarily stopped this error from crashing my app by changing Tab's indicator's Animated.View to transform to: ``` transform: [ { translateX: isNaN(indicatorTransitionInterpolate) ? value * (WIDTH?WIDTH:0) : indicatorTransitionInterpolate,...

@richstokes Yes, you are right; I also got those "field sizes are different" exceptions each time along with the main exception. @richstokes Question for you: Do you have _multiple_ sets...

@richstokes Yes I did disable the animation and that has SOLVED the crashing. I did so by editing node_modules/@rneui/base-edge/dist/Tab.js changing the transform-translateX near the bottom of the file to be...

I hate to nag, but umm: Could something be done about this problem? It is preventing me from publishing my app, which my company and clients depend on. I cannot...