<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Mobile on Jake Worth</title><link>https://jakeworth.com/tags/mobile/</link><description>Recent content in Mobile on Jake Worth</description><image><title>Jake Worth</title><url>https://jakeworth.com/twittercard.png</url><link>https://jakeworth.com/twittercard.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 02 Sep 2021 13:51:03 -0400</lastBuildDate><atom:link href="https://jakeworth.com/tags/mobile/index.xml" rel="self" type="application/rss+xml"/><item><title>App Store Delays</title><link>https://jakeworth.com/tils/app-store-delays/</link><pubDate>Thu, 02 Sep 2021 13:51:03 -0400</pubDate><guid>https://jakeworth.com/tils/app-store-delays/</guid><description>&lt;p&gt;Here&amp;rsquo;s an observation from a month of developing for iOS. There can be a delay
on any action taken in the App Store Connect console that you should plan for.&lt;/p&gt;</description></item><item><title>Clear iOS Mobile Dependencies</title><link>https://jakeworth.com/tils/clear-ios-mobile-dependencies/</link><pubDate>Thu, 02 Sep 2021 11:32:04 -0400</pubDate><guid>https://jakeworth.com/tils/clear-ios-mobile-dependencies/</guid><description>&lt;p&gt;When working on a React Native app on the iOS side, switching between branches
with different dependencies can wreak havoc on your development environment. To
ensure they&amp;rsquo;re you&amp;rsquo;re running the right libraries, blow everything away and
start over:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;rm -rf node_modules &amp;amp;&amp;amp; yarn &amp;amp;&amp;amp; (cd ios &amp;amp;&amp;amp; pod deintegrate &amp;amp;&amp;amp; pod install)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Replace &lt;code&gt;yarn&lt;/code&gt; with &lt;code&gt;npm install&lt;/code&gt; if you&amp;rsquo;re using NPM.&lt;/p&gt;</description></item><item><title>Scroll on XCode Simulator</title><link>https://jakeworth.com/tils/scroll-on-xcode-simulator/</link><pubDate>Wed, 25 Aug 2021 16:46:48 -0400</pubDate><guid>https://jakeworth.com/tils/scroll-on-xcode-simulator/</guid><description>&lt;p&gt;To get mobile scroll behavior on the XCode Simulator, inside the simulator
window you must left click, then scroll.&lt;/p&gt;</description></item><item><title>React Native Shake</title><link>https://jakeworth.com/tils/react-native-shake/</link><pubDate>Fri, 13 Aug 2021 14:37:36 -0400</pubDate><guid>https://jakeworth.com/tils/react-native-shake/</guid><description>&lt;p&gt;The &amp;lsquo;shake&amp;rsquo; is an important React Native feature; it opens the In-App Developer
Menu. This menu lets you reload, open the inspector, monitor performance, and
more. To &amp;lsquo;shake&amp;rsquo; your simulated device, press &lt;code&gt;^ ⌘ Z&lt;/code&gt;. An alternative hotkey is
&lt;code&gt;⌘ D&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>TestFlight Downloads Latest Build</title><link>https://jakeworth.com/tils/testflight-downloads-latest-build/</link><pubDate>Fri, 13 Aug 2021 12:17:08 -0400</pubDate><guid>https://jakeworth.com/tils/testflight-downloads-latest-build/</guid><description>&lt;p&gt;When you push an iOS build to TestFlight, what&amp;rsquo;s the experience for your
testers? Do they need to opt-in to test the latest build?&lt;/p&gt;
&lt;p&gt;Speaking anecdotally as person who has pushed a build and plans to test it
today, when you add that build to your test group, it is automatically
downloaded as the default for each of your testers, replacing the previous
build. You can visit the TestFlight app on your phone to see the apps you can
test. The latest build (build number, an integer, not the SemVer version)
should be automatically downloaded to your device.&lt;/p&gt;</description></item></channel></rss>