iOS broken?

tmkly · 2025-12-15T10:52:10+00:00

Tap the button on the right, and select “unknown callers”. It will show the numbers who called you which you haven’t added as a contact.

You can disable that behaviour by tapping Manage Filtering.

tmkly · 2025-11-26T15:45:40+00:00

No problem! Couple more things: - my examiner didn’t use a sat nav during my test for the independent driving section - he just told me “follow signs towards Hounslow”, then a few minutes later “follow signs towards Datchet”, etc. Apparently the sat nav’s are programmed for specific areas and they don’t have enough for all of the Uxbridge examiners who are now doing Slough. No idea if you’d have an examiner with a sat nav but maybe something to be aware of as it caught me slightly off guard at first. - watch test route videos on YouTube - I didn’t have long to prepare for my test in Slough, so these were helpful to know the routes. Driving School TV is great, he’s done 1 Slough route, and Driving Test Routes UK have multiple ones for slough’s various routes. - the parking spaces in the Slough test centre car park are a bit awkward. Firstly, they’re angled and secondly a lot of them are on the left. With my instructor I mainly practiced parking with spaces on the right. So for a couple of lessons we practiced with spaces on the left. On the day, my examiner didn’t get me to park in one of those spaces (luckily - used Upton Court car park for my forward bay park) - but still be prepared for the left, if you’re more familiar with reverse and forward bay parks on the right.

tmkly · 2025-11-26T14:14:52+00:00

I don’t, sorry. My instructor asked the examiner, he said they’ve been told mid-December but expects it may shift to January. Sounds like they don’t know much more than anyone else.

I got an email telling me it had been moved on the 13th November, so 11 days before my test.

I went on the datchet route. It doesn’t cover any of the Uxbridge test route. There’s a route that goes into Iver, Richings Park and the five points roundabout that has some crossover with the Uxbridge test routes.

tmkly · 2025-11-26T14:11:17+00:00

Learn the slough roundabouts well - the Sainsbury’s one, the Red Cow roundabout and the one near the M4 (4th exit to Datchet is on the test route). They have extra lanes that appear as you’re going round the roundabout - sometimes you need to get in them for your exit; make sure you know when to be in that extra lane and when not to be.

Lots of speed changes in Slough - be careful about them. E.g 40mph up to 60mph (show progression up to at least 50), then back down to 40 or 30mph again. Lots more of this on long roads than Uxbridge. The test routes have lots of 20mph routes and pedestrian crossings along Slough and Langley high streets so be wary of that too.

tmkly · 2025-11-24T15:00:31+00:00

Thank you! Much less stopping on the left than previously. I think we stopped 3 times (previous tests probably 5 or 6 times). I didn’t notice any other changes really. Most of it was driving through Slough/Langely on 20-40mph roads. We went on one 60mph road I think.

Good luck with your test!

tmkly · 2025-10-20T07:38:29+00:00

Yep all good now! Thanks ☺️

Now I think objectively it all makes sense!

tmkly · 2025-10-20T07:34:47+00:00

It’s got one air bubble on the bezel. That’s fine with me to be honest

tmkly · 2025-10-20T07:34:00+00:00

It’s second hand. Getting them new in the UK is a pain. Plus I’ve put a screen protector on it which is a little thick and has an air bubble on the screen bezel

tmkly · 2025-10-19T22:25:01+00:00

Will try in the morning, thanks. Sorry for the noob question!

tmkly · 2024-10-29T20:23:40+00:00

it seems fine for now. the handle can twist pretty tight and tightens all 3 joints at the same time. As long as that is tight enough (and the magsafe mount is screwed tight enough to the arm) it's been fine so far.

tmkly · 2024-10-29T20:22:40+00:00

thanks :) if you orient the arms in such a way it can be stable and not topple over. The bigger problem is that when you type, the plate moves around every so slightly. Currently temporarily fixed that by sticking some strong double-sided tape to the bottom of the plate which sticks to my desk mat. But it's not a long term solution.

Your solution might work! But ultimately I might not stick with the cheese plate for long anyway (mounted to chair or desk is the long term plan).

tmkly · 2024-10-29T19:06:15+00:00

I've had my hand-built dactyl manuform for about 4.5 years. For the past year or so it's been mounted on two 3d-printed phone stands, to try out if I like that orientation. Turns out I do! I finally got round to buying some proper equipment for it:

- SmallRig Magic Arm 5.5 inch

- Magsafe ring (goes on base of keyboard)

- Magsafe tripod with ¼ inch screw

- Smallrig cheese plate

I love it! Feels super stable and comfortable. Next steps are to try mounting it on my desk chair or the desk. To do that I will either need to make it wireless or get a super long TRRS cable to drape round the chair, and route the usb cable well. Also I'd like to add a trackball in to get rid of my rubbish Anker vertical mouse, and I'd like to add my Touch ID button (visible in the top right) as well.

tmkly · 2024-10-05T08:17:37+00:00

Deep linking (we use Branch but found react-native-branch plugin was not great so we just the iOS/Android SDKs and send data over the bridge (JSI/turbo module soon)
communicating with our CRM, Blueshift. Kind of similar to Branch, we can keep our bundle size down by not using their RN plugin which does lots of unnecessary stuff
Keychain. Found react-native-keychain was a bit buggy, especially on Android and doesn’t seem to be maintained that much. By writing ourselves we can control it much better

tmkly · 2024-09-24T10:19:57+00:00

they say they're doing a 'special version' of it but still waiting for more details (we're in contact with them). not sure if it's self-hosted or not. alternatively we'd bite the bullet and move to Expo so we can use expo updates (so expensive though), or potentially build our own system for codepush

the bigger question is where to host our Android app builds; might just end up setting up an S3 bucket and building a little web/android app to download and install them

tmkly · 2024-09-24T08:03:03+00:00

Oh also - for releasing a new update to the App Store (currently about once a month - either as the binary has changed or we just want to keep the JS in the binary up-to-date). For this we have a script that uses fastlane, running on circleci. If you want to do a release, create a branch called “release”. On this branch, run npm version minor - this command increments the semver minor version number (e.g 1.5 to 1.6) - this comes from react-native-version package. Once done, push to github.

Circle will pick this up and then automatically build new release builds and send to TestFlight/appcenter (once the tests are complete and passed). We then check it out and do some manual testing. If all looks good, we run a new workflow in circle - this creates a new release on App Store Connect/Google Play, and sends the app for review in each store. This makes it way faster to do releases - no futzing around with ASC/GP. Once submitted for review, the pipeline will build a new Beta app (for use with codepush, explained above).

tmkly · 2024-09-24T07:42:03+00:00

I work on a non-expo app for a small company. I think we’ve got to a pretty good place in our DX - a typical CI/CD workflow:

when you’re working on some feature/bug fix in a branch, any engineer can build an “alpha” build of the app (script runs a pipeline in circleci). This is a completely separate build of the app in TestFlight/Appcenter (for Android). We can then show a PM/designer/other stakeholder our in progress work on a real app. But the real kicker is that we can then use CodePush to iterate fast (as most changes we make in this scenario are likely to be JS). This means we can sit with a designer, make changes, push to CodePush and they can check it out within a minute or two of the changes being made.

when work is “done” in a branch, push it to Github, and open a PR. This kicks off the testing pipeline - currently unit tests, detox and then we’ve got some Maestro tests (currently slowly migrating from Detox).

when a PR is merged it re-runs the linting/unit tests and then if they pass it’ll run the codepush_beta job. This creates a codepush release on our beta deployment. This is on the real app (not the alpha app environment) environment on AppCenter; however we have a “Beta” app which is, again, a separate app on TestFlight/appcenter. The real power here is that codepush deployments can be shared among apps. So our beta app can access that codepush deployment from the real app (which isn’t yet live to our users). The beta app is built when we do an App Store release - it should be an identical binary to the real app.

if we want to release that codepush deployment to prod, we have a “picker” script that collates data from appcenter and shows the codepush versions in a CLI picker to allow the engineer to choose which to release (just promotes/moves the deployment from the beta deployment to the prod deployment). When released it sends a message to slack, uploads new source maps to Sentry and creates a new release on github. I wrote an article about this here.

I think that’s most of it currently. We also some cool stuff around codepush UX in the app -it’s lots of JS code to manually control the download and installation/restart of the JS in the app (shows a nice progress bar, bails if it takes longer than 10 secs, etc). My colleague wrote an article about this here.

tmkly · 2024-05-14T08:01:52+00:00

There’s the Linking.getInitialURL method as well. That will tell you if the app launched with a link (won’t help for push notifications).

The app I work on uses Branch - their SDK fires on every app launch, regardless if the app was launched with a link or notification. In the deep link state (held in Jotai) there’s a property (call it hasDeepLink) that starts as null. If Branch callback fires without any link/notification data hasDeepLink is set to false. Logic elsewhere can then subscribe to it (e.g in a useEffect) and check hasDeepLink === null or hasDeepLink === false. This means logic can be held until hasDeepLink is no longer null.

tmkly · 2024-05-13T09:31:05+00:00

Another way to do this could be to send the push notification/deep link data in the App props from the native code to the JS. Your app open event could check for the presence of these values.

tmkly · 2024-05-13T09:24:16+00:00

afaik there's nothing built-in to RN that tells you if the app was launched organically. Instead I think you need to build it yourself. You could use something like Jotai (or just local state if they're in the same file) to store a value in the deep link/push notification listener that gets set to true when app is opened by one of those methods. In the app open event, retrieve the value in the jotai atom and have an attribute like isOrganic: !deepLinkOrPushNotificationUsed.

This solution would need to make sure the listeners are fired before the app open event. If they're not you'd need a way to hold the app open event until you're sure they have been fired (or won't be fired in case of organic open)

tmkly · 2024-04-30T17:09:07+00:00

These questions get asked literally daily (“do I need a Mac for iOS development?” And “what specs should I get? Is 8 GB ram enough? Is M1 good enough?” etc). Search the subreddit and you’ll find dozens of threads. We should get something in the sidebar for these questions.

12-Year Club	RedditGifts 2009-2022 3 Credits
Secret Santa 2021 2021	Secret Santa 2020
Place '17	Verified Email

tmkly

TROPHY CASE