Skip to main content

React Native Experiments - Tips & Tricks

 When it comes to develop native apps but with single code base, React Native is much popular choice to use for mobile apps development. With my experience I observed that there are a lot of side things that some times produce blocker or irritate us as a developer, so I thought lets list all those things here in single post and I will try to update this post in future as well. 

First thing I faced was application give error as soon as we run it in debugger mode. So for that issue I found that we need to clear the cache in network tab on debugger side which usually opens on default url like this : http://localhost:8081/debugger-ui/

And as we can see in network tab, check the Disable cache option and reload the app in debugger mode, it should start working fine.


Popular posts from this blog

C# Anatomy of Async and Await - Part 1

This is first part of C# Anatomy of Async and Await series, feel free to go through all parts listed following : Part 1 Part 2
I am using async and await keywords from quiet along time and feel that should be explained in light of my experience with them. There are many use cases of them but generally need them when we don't want our program to get halt while making some  API call ( http / web request ). Some other use cases are :CPU bound task that took time ( using Task.Run )Accessing file resources ( async streams )etc.Above was little context that will help us understand the internal working of an async task, lets jump right into points that will help us to understand the anatomy and describe some brief explanation so that we can understand it clearly, so the first point is : 
# First, we use async with a method which has await keywo…

C# Anatomy of Async and Await - Part 2

This is second part of C# Anatomy of Async and Await series, feel free to go through all parts listed following : Part 1 Part 2
Today we are going to see some of the best practices to get maximum out of Asyn & Await in C#. First it is not recommended at all to call asynchronous methods synchronously but lets say in some situation we have to some how, then we should make sure that we are not calling  

Synchronization context is another key factor which we usually ignore, it means that to return execution control to the same thread which started that asynchronous task, it is important when the stater thread is UI but it make no sense if it was not main / UI thread, in that case the cost of context switching will be apply and overall performance of the application will hurt. So the rule is if its a web app / api apply ConfigureAwait(false) f…