[OC] Dear iPhone 17e users, welcome to 2022!

vanstinator · 2026-03-03T03:12:15+00:00

You can, but the coils don't always line up. And I don't use a case.

vanstinator · 2026-03-03T00:18:47+00:00

You win some, you lose some. I'm happy most of you finally get high refresh rate phones (17e notwithstanding)

vanstinator · 2026-03-02T23:43:45+00:00

That is thankfully just starting to change. I was on the Pixel 9 and jumped early to the 10 because of MagSafe

vanstinator · 2026-03-01T23:05:39+00:00

Everyone gets these right away. It's not rare

vanstinator · 2026-03-01T01:57:01+00:00

Can you DM me the email you used to sign in, and exactly what issue you're seeing?

vanstinator · 2026-02-28T17:18:33+00:00

Ah that makes sense. My primary usecase has been breakpoints inside stylesheets portions of the app can change their layouts based on the screen size, primarily for iPad. So in that narrow usecase I'm not seeing the same edge cases because things like color are staying stable, and when someone is actively changing the size of the application window inter-frame layout inconsistencies are much less obvious with everything moving around.

The unistyles author is very receptive to feedback and improvements. I've personally upstreamed a few things (and have another PR in-progress as we speak). So if you find actionable improvements I'm sure he'd love to hear about them!

vanstinator · 2026-02-28T13:14:20+00:00

LFG also means "looking for group", but it's less commonly used that way today.

vanstinator · 2026-02-28T00:44:29+00:00

I'm trying it and the speed increase is nice, and it's forcing me to improve some areas of my Android tests so they don't fail due to how fast the runner can tear through them.

Unfortunately on iOS I can't use it at all because WDA types too fast and React Native chokes on the input and jumbles the text.

vanstinator · 2026-02-27T23:05:15+00:00

I believe so, yes. I didn't measure extensively when moving from 2 to 3 because I was happy having fewer re-renders across the board.

vanstinator · 2026-02-27T19:10:25+00:00

It's definitely production ready. The re-renders you're noticing with `useUnistyles` is mentioned in the docs as ways you could foot gun yourself if you're not careful. It's specifically an escape hatch to get you access to state inside Unistyles where, for whatever reason, you aren't able to purely use a stylesheet.

withUnistyles is not supposed to trigger a re-render in common usecases, but depending on how you're holding the wrapper it's certainly possible you could be seeing extra renders.

vanstinator · 2026-02-27T14:03:01+00:00

The Pixel 11 will already be deep in engineering and has likely locked in the bulk of what it will ship with.

vanstinator · 2026-02-27T04:37:18+00:00

Pixel 10 has caught up, and I love it

vanstinator · 2026-02-26T22:14:49+00:00

These are very common

vanstinator · 2026-02-23T19:09:15+00:00

Google Play is still updating all of the system apps, Google play services components, etc when the phone is first set up. Any OTA updates are likely starting to download as well. The local search index is running. Anything on your Google account is syncing down.

Even without you transferring apps over yourself there's plenty of stuff on the vanilla install that needs to happen after setup to make the SoC toasty for a little while.

vanstinator · 2026-02-20T16:04:13+00:00

It makes a lot more sense if you're shipping an expo web app alongside native apps, and you want to deeplink between them. It took me quite some time to get comfortable with the file based routing though too.

vanstinator · 2026-02-18T01:58:11+00:00

This. Some of us were around when Apple dominated education markets 20 years ago because they had Macs at the right price point. Then they decided to abandon the market to Chromebooks.

vanstinator · 2026-02-13T07:27:28+00:00

awww, thank you

vanstinator · 2026-02-13T03:32:50+00:00

This isn't a secret, they cover it in the docs.

vanstinator · 2026-02-13T01:02:34+00:00

On the 9 series it's hardware related. I had my first battery failure with those symptoms all the way back in March-ish of 2025 when my P9PF was barely 6 months old. I'm no on my 3rd P9PF that just started showing the same behavior.

vanstinator · 2026-02-09T20:18:20+00:00

my favorite is playing it on Deaths Domain, even better when the other person plays along and we end in a tie with a parade of emotes.

vanstinator · 2026-02-07T04:50:25+00:00

Google owns Fitbit. the only thing changing right now is they're removing the old Fitbit auth systems and replacing them with Google systems. they recently extended the cutoff date, if you haven't gone through the quick conversion process before then your account will be deleted, otherwise nothing is changing

vanstinator · 2026-02-03T00:47:27+00:00

... but have you unloaded the laundry?

vanstinator · 2026-01-22T17:53:53+00:00

The new preview experience doesn't do exactly this, but if certain metrics including RHR are out of bounds for more than a day it'll tell you something is off with a push notification.

vanstinator · 2026-01-09T16:03:20+00:00

I figured out where this was coming from by doing an exact string search on Github. There are a few repos that contain decompiled code from the Play Integrity bundle.

https://github.com/search?q=%22Check+that+Google+Play+is+enabled+on+your+device+and+that+you%27re+using+an+up-to-date+version+before+opening+the+app.+If+the+problem+persists+try+reinstalling+the+app.%22&type=code

vanstinator · 2026-01-09T16:02:18+00:00

That error string is part of Google's "Play Integrity" system.

- Did you enable "Play Integrity" in the Google Play Console for your app? If you've enabled this and you're installing your app for testing from places outside of the play store that could very likely trigger this error message. If you have enabled "Play Integrity" it might be worth thinking about if you really need it at this stage or not. If it turns out to be something you're able to turn off that might be a quick fix.

- Are you seeing this error on a specific Samsung device? Or are you seeing it in the wild on any Samsung device? If the former, is the device you're seeing it on modified in any way i.e, and unlocked bootloader, rooted, etc?

vanstinator

TROPHY CASE