Question: I have a received a server log which has entries for each row with date something like this below. 

23:18.6

23:23.6

I want to convert these dates in DD/MM/YY HH:MM:SS format in excel, but when I do this I get value like 00/01/1900 00:23:19 

Please can you some let me know what kind of format is this date/time entries.

Answer: 
I agree with Scott Helme's point in another answer here. But in some extreme situations (security issues, API breaking changes...) where you absolutely need the users to update to continue using the app, you could provide a simple versioning API. The API would look like this: 

versionCheck API: 

Request parameters:

* `int appVersion`

Response

1. `boolean forceUpgrade`
2. `boolean recommendUpgrade`

When your app starts, you could call this API that pass in the current app version, and check the response of the versioning API call. 

If `forceUpgrade` is `true`, show a popup dialog with options to either let user quit the app, or go to Google Play Store to upgrade the app. 

Else if `recommendUpgrade` is `true`, show the pop-up dialog with options to update or to continue using the app. 

Even with this forced upgrade ability in place, you should continue to support older versions, unless absolutely needed.
I highly recommend checking out [Firebase's Remote Config](https://firebase.google.com/docs/remote-config/) functionality for this.

I implemented it using a parameter - app\_version\_enabled - with a condition "Disabled Android Versions" that looks like this:

```
applies if App ID == com.example.myapp and App version regular expression ^(5.6.1|5.4.2) 

```

Default for the parameter is "true", but Disabled Android Versions has a value of false. In my regex for Disabled Android Versions, you can add more disabled versions simply with another `|{version name}` inside those parentheses.

Then I just check if the configuration says the version is enabled or not -- I have an activity that I launch that forces the user to upgrade. I check in the only two places the app can be launched from externally (my default launcher activity and an intent-handling activity). Since Remote Config works on a cache basis, it won't immediately capture "disabled" versions of the app if the requisite time hasn't passed for the cache to be invalidated, but that is at most 12 hours if you're going by their recommended cache expiration value.