We are trying to think of a way to migrate our users from using UDID to identifierForVendor.
To migrate, we are thinking to submit an update before May 1st that uses both UDID and identifierForVendor so that we can identify the user and migrate him to the new system.
And here comes the problem :
Let's suppose that two months later we need to update our app again. We will no longer be able to access the UDID, so we will not be able to keep the code that migrates the users.
If a user fails to install the first update of our app and migrate himself, then if he downloads the 2nd update of our app directly, we will not be able to migrate him.
Is there a solution to this problem ?
Related
According to this answer, I want to use an offline first db inside my electron app. I nedd that the users are not able to directly modify the database, but they can only read data using the UI. The data needs to be synced with a master remote client app that will add and modify data. Can anyone suggest me a good database library to do this?I have a pusher account and an heroku one, that can be used to pass the data between the clients, but first I need a way to store them into the app
I'm currently working on a React Native application, the server is already implemented and my app should implement offline sync, I'm planning to integrate realm on the mobile device to deal with the offline data and pushing the data to the implemented server when the device is online. How would I go about doing that?
I'm trying also to make some kind of offline sync. A calendar app that works offline.
I'm developing it on ionic 4 using sqlite.
Basically, what I did is: I keep a variable with my last update timestamp.
Part 1
Get activities.
A service is running on the background, getting from the backend activities that their creation timestamp is later than the mobile last update timestamp.
Part 2
Every time the user create an activity I add the timestamp to the activities table and a flag called synced that is true / false.
Another service scans the table for synced === 'false' and does the POST request.
Hope I helped.
Having a WPF app we've got a server that lets the user to install using ClickOnce distribution. The issue here is the link we provide changes to hide real filesystem.
First time the user tries to install the app, everything goes well; the .application gets launched remotely and the app gets installed.
Next time the user wants to update the app, if the link provided is differente (because of a token or a differente sub-path) the user will receive a DeploymentException saying that the same app is already installed from a different location.
Is there a way to allow the app to be installed from any location we provide?
Thanks!
UPDATE 1:
Let me explain what we've got so far:
We have a web server that publishes a folder where the app lives. The path depends on some factors so it may change. if the user wants to install the same app from a different url path, it will fail.
Something like:
http://site.site/app_15/App.application
http://site.site/app_16/App.application
being app_15 and app_16 the same app but installed on different dates and admin sites.
In Sitecore you basically have three databases. The Core, Master and Web database.
Simply put the Core database holds all Sitecore settings. The Master database is the authoring database. So it contains all versions of any content.
Then in Sitecore you can "publish" the contents and it will publish the latest version of each content to the Web database.
So suppose I have a website with a news page. And a user is able to edit a news item from the web site (so not through the CMS). How would the database then get updated when it's set up like this?
It would probably update the Web database, but then when I go into the CMS I don't see the latest changes, since the CMS reads from the Master database, right?
So does that mean that it should write twice? Once to the Web database and once to the Master database?
Can anyone tell me how this works in Sitecore or the like?
The reason I'd like to know this is becasue I'm thinking of creating a similar database setup. And I'm just not sure how to solve this issue.
When you have items that needs to be updated by the website visitor, you need to use the SitecoreService SOAP webservice or create your own custom webservice that runs on the Master-instance and triggers a publish after updating.
Well, Sitecore has a publishing step. When the user publishes in Sitecore, it updates the Web database at that point. If you want to build a similar system, I would simply store all versions of an item in the Master database and only when the user chooses to publish, copy the latest version to the Web database.
If your site
- generates a lot of comments
- generates the comments continuously
- uses multiple content delivery servers
- requires CMS users to manage them
I would not store the comments as content items.
The reason is HTML cache and publishing behavior.
On high volume site you'd most certainly use html caching to achieve best possible performance. If a publish is required to show comments, you'd need frequent publish actions and thus html caches are cleared often.
You don't wan't that :-)
Modeling after the DMS implementation is the safest (not cheapest and Datatables isn't something I recommend these days), storing stuff in a separate database, possibly using queuing to prevent an overload if things get busy..
I have just completed a migration from a master/slave to HRD. During this migration I was forced to change my app name from myapp.appspot.com to myapp-hrd.appspot.com. I have set up an alias so my users can still use the old site url.
But I find it rather messy to have two apps where the one just forward requests to the other.
Is there any way I can migrate my new myapp-hrd back to myapp?
The only way I can think of is to erase my old myapp and then migrate from myapp-hrd to it, but it takes 3 days to delete an GAE app. And 3 days downtime is not an option. I have to keep myapp running since the url is hardcoded in a lot of android phones.
Even if you delete your old app, you won't be able to create a new app with the same identifier. Did you use the migration tool? If so, the new application should now be serving both the new and old app URLs. Otherwise, I recommend you report a production issue so that someone from Google links the apps manually.