DEV Community: Victor Corvalan

UISearchDisplayController crashes on iOS 13

Victor Corvalan — Sun, 02 Feb 2020 12:32:06 +0000

The UISearchDisplayController is fully deprecated on iOS 13 and was deprecated since iOS 8. I'm maintaining an APP that is live since 2012/2013 that was using it.

Last week we received a ticket reporting a crash when a user tries to enter on a part where there is a search bar on it.

One important thing to note is while testing the APP running directly from XCode or generating the .IPA everything seems to work fine (our testers didn´t get any crash or any strange behaviour), only when the build is submitted to the APP STORE to test it through Testflight you get the crash. We couldn´t reproduce the crash in a dev environment no matter what type of build we setup, how we setup the scheme or how we generate the IPA just like the APP STORE does for example to install on the device.

That ViewController had some implementation of the UISearchDisplay that we removed, and also we notice that in the storyboard, the ViewController had some references...

Hope that this help if you are maintaining and old iOS APP and start receiving crashes reports that you can't reproduce on your environment. If you need to replace the old UISearchDisplayController, take a look to this tutorial from Ray Wenderlich.

Setup auto-renewable subscriptions for iOS in Flutter

Victor Corvalan — Fri, 25 Oct 2019 10:06:51 +0000

After I had successfully tested and implemented auto-renewable subscriptions on my Android APP… it was time to do the same thing for iOS… but once again… a problem came up.

When I was trying to list my past purchases, on iOS I was receiving an empty list… I won’t write about a full implementation of in-app purchases in Flutter as I’m only interested in this specific problem… you can get a good tutorial from Fireship.io.

The thing is, on iOS, you need to call completePurchase() in purchaseUpdatedStream.listen … just before you complete a purchase (yeah)… something like this

InAppPurchaseConnection.instance.purchaseUpdatedStream.listen((purchases) {
 purchases.forEach((purchase){
 if (purchase.status == PurchaseStatus.purchased) {
 if (Platform.isIOS) {
 InAppPurchaseConnection._instance_.completePurchase(purchase);
 }
 }
}

If you are following the tutorial from Fireship.io… I’ve added that call inside _verifyPurchase(). They added the completePurchase call in _getPastPurchases() but nothing happens if you call from there because you are going to receive always an empty list of past purchases if you don’t “confirm”.

Your Flutter APP has one or more issues

Victor Corvalan — Mon, 21 Oct 2019 02:25:58 +0000

It was the first time that I was submitting a Flutter APP to the App Store… I thought that everything was ready… I’ve tested on several emulators, on real iOS devices… and everything went smoothly and without a problem when I uploaded to the App Store… but after their system finished processing my build, I received an email from Apple…

ITMS-90338: Non-public API usage — The app references non-public symbols in Frameworks/Flutter.framework/Flutter: _ptrace. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed.

To avoid that issue… you should run

flutter build ios — release

Then in xCode , go to Product->Scheme->Edit Scheme … and make sure that Build Configuration is in RELEASE for ** Archive**

And now you are ready to publish!

Flutter Fatal Exception in Firestore Android

Victor Corvalan — Sun, 20 Oct 2019 00:15:34 +0000

Flutter Fatal Exception in Firestore Android

Yesterday I was facing an unexpected crash in production (How did this happen?) to be short, I do not own a physical Android device to test RELEASE builds, in theory I was adding a small, almost insignificant change… but doing some Flutter Clean here, Flutter Package Get over there, Android CLEAN, Android BUILD and that kind of things… SOMETHING IMPORTANT DID ACTUALLY CHANGED.

FATAL EXCEPTION: main
Process: com.app.android, PID: 12668
java.lang.RuntimeException: Internal error in Firestore (19.0.0).
 at com.google.firebase.firestore.g.j.a(:379)
 at com.google.firebase.firestore.g.g.run(Unknown Source:2)
 at android.os.Handler.handleCallback(Handler.java:873)
 at android.os.Handler.dispatchMessage(Handler.java:99)
 at android.os.Looper.loop(Looper.java:193)
 at android.app.ActivityThread.main(ActivityThread.java:6718)
 at java.lang.reflect.Method.invoke(Native Method)
 at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

After digging and digging and trying to figure out what was happening, I realize that disabling useProguard and minifyEnabled I was able to fix that crash… BUT what the hell?? I didn’t change or add any proguard rules or gradle file… so, finally found WHAT was actually causing that crash thanks to my GIT file status… and guess what I’ve found…

android.enableR8=true

Some how R8 got added AND enabled in my gradle.properties file!. Changing the value to FALSE got my APP running and free of crashes.