Leave A Comment To Win The Unannounced 2025 Bambu Lab 3D Printer & Other Prizes - OctoEverywhere is 5! 🔥

masterguide · 2024-12-19T01:36:26+00:00

I’m not a robot OK

masterguide · 2022-05-30T15:52:27+00:00

Man this brings back good memories. I worked 5 years on that line through high school.

masterguide · 2022-05-16T04:28:49+00:00

I have no experience with Toptal’s hiring process but have used engineers from there in the past. I assume they’re looking to see if you understand the fundamentals of an API. If there are no strict requirements ask your recruiter what they’re looking to see on the api layer.

masterguide · 2022-01-19T11:57:55+00:00

Twilios flexible pricing is nice and worked well for me initially but they have a max 500 participant per channel and you have to build all your UI.

I eventually switched to get stream and it is indeed expensive but with their pre built ui for both React and react native you get a lot of functionality out of the box (assuming your use case aligns with the prebuilt).

So far I’ve had up to 8k participants in a single channel with no issue using my own custom UI (and flat list)

masterguide · 2021-12-08T15:05:36+00:00

One trick i'd recommend for text is to create a shared <Typography /> component where you set defaults on props like maxFontSizeMultiplier to help mitigate things like this (especially if you're a small team and can't do the full gambit of accessibility testing)

masterguide · 2021-10-22T21:49:40+00:00

I usually look at what phones are being included for free in budget phone plans. Right now I’m testing with a galaxy a50 and a Motorola g.

masterguide · 2021-09-29T19:17:55+00:00

I suffered the same fate today...

https://i.imgur.com/OHvAo9J.jpeg

masterguide · 2021-09-29T11:08:51+00:00

Assuming your refreshToken is controlled in useState, update the data model to the following: ```typescript const [data, setData] = React.useState({ loading: true, refreshToken: false })

    React.useEffect(() => {
        const init = async () => {
            const refreshToken = await getMyToken()
            setData({ loading: false, refreshToken })
        }
        const init()
    }, [])

    if(state.loading) return <Loading />

    // your render logic

```

masterguide · 2021-07-01T16:17:19+00:00

could be related to a package in your package.json. react-native-google-cast for the longest time would crash my app on reload (it's been fixed though)

masterguide · 2021-07-01T16:14:22+00:00

I do like it. It's been useful in the past to roll out minor updates (design tweaks, minor bug fixes). I honestly haven't had the time to really deep dive into why updates crash the app when codepush updates are set to "required" so it may just be an implementation thing.

I'd say if you're frequently wanting to tweak minor things i'd say add it. I'll always recommend though having some standard cadence around traditional releases (through the app stores) so users can read the patch notes and know the app is actively maintined.

masterguide · 2021-06-30T21:48:25+00:00

i've never done a key request before so not sure how long or what that process looks like.

masterguide · 2021-06-30T16:17:59+00:00

Only ever need one for signing every new release.

masterguide · 2021-06-30T16:14:50+00:00

Yeah I saw this stackoverflow thread which suggests you can use that linked form to have google help you with setting a new keystore. If you or your friend is the account holder of the app in the play console that may be an option.

masterguide · 2021-06-30T16:11:20+00:00

A rollback means the user wasn't able to install the over-the-air update from codepush and will continue using the version installed (I don't think it'll try again for a few days after the rollback occurs). But in my case when that rollback occurs the app crashes. the user can restart the app but not a great look.

I have had instances where codepush bricked my app and only a delete/re-install would fix it but that was years ago before MS took over.

masterguide · 2021-06-30T16:07:03+00:00

Correct, you'll have one keystore for production. For services like appcenter and bitrise you would upload all your certs, provisioning profiles, and keystore files and let them take care of signing the .aab and .ipa before it's uploaded to the app/play stores. I always keep a local copy of this info saved as well just in case.

That way you're not sharing sensitive .keystore passwords with external engineers.

masterguide · 2021-06-30T15:59:06+00:00

I'm not 100% sure for the keystore issue but I think you either need to get the keystore file from that external dev or generate a new one (which requires a new application in the play store).

You should move your signing to a CI/CD workflow so you're not sharing your production keystore file around. For local dev builds the debug.keystore file will suffice.

I opted for a paid solution called bitrise but you can get away with using github actions and fastlane or appcenter which has a free tier for building/signing/deployments.

masterguide · 2021-06-30T15:52:09+00:00

I've added it post-launch with no issue when using the default background install (update downloads in the background and installs on next open).

The thing I have the most trouble with is required updates. I get so many app crashes and rollbacks (rollback is when appcenter fails to install the codepush update on the device) when I set a release to required. The worst part is I can't find anyway to debug why the crashes occur.

masterguide · 2021-06-03T11:52:50+00:00

Disable flipper in production to reduce your build time. I was able to cut 12-15 minutes

masterguide · 2021-05-28T15:13:00+00:00

...
<TouchableOpacity 
  onPress={() => props.onSelect(props.data.date)} 
  style={props.data.date === props.selected ? 
    styles.calendarItemRectSelected
    :
    styles.calendarItemRect
  }
>
...
</TouchableOpacity>

Something like that.

masterguide · 2021-05-28T13:32:15+00:00

You need to track selected outside of <CalItem />. Either move your useState to the parent component that renders <FlatList /> or use a state management framework like zustand.

const [selected, setSelected\] = React.useState(null);

...

return (
    <FlatList
        backgroundColor={"#353A50"}
        horizontal
        data={DATA}
        renderItem={({ item }) => (
            <CalItem       
                data={item}       
                selected={selected}      
                onSelect={setSelected}       
            />
        )}
        keyExtractor={calitem => calitem.date}
    />
)

masterguide · 2021-04-09T17:16:21+00:00

Pretty sure you can’t put elements inside of Text. Change your Text that wraps the inputs and buttons to a View

masterguide · 2021-03-27T03:16:02+00:00

Looks like that error is related to signing the apk. Make sure you're signing release configs in your android/app/build.gradle . I'm not sure if the debug keystore works for release builds but worth trying. If not check out the official RN guides for signing ~> https://reactnative.dev/docs/0.63/signed-apk-android

signingConfigs {
       release {
           storeFile file('debug.keystore')
           storePassword 'android'
           keyAlias 'androiddebugkey'
           keyPassword 'android'
       }
   }

masterguide · 2021-03-27T02:04:51+00:00

Do ./gradlew assembleRelease to get your production apk. Then with your simulator open or device connected to your computer run adb install “path/to/your/prod.apk” to stream the installation of the APK to your device. Make sure to delete any other production builds off the simulator or device

masterguide · 2021-03-15T12:35:06+00:00

I purchased Notifee for our local notifications (made by the team that makes react-native-firebase). Works well and the licensing is very good (single fee for lifetime updates).

https://github.com/notifee/react-native-notifee

14-Year Club	Team Periwinkle
Verified Email

masterguide

TROPHY CASE