I want to move the Browser tokens I have collected from one vendor to another. It seems when I am trying to move it, the other vendor says that tokens would be lost.
Does anyone know how can we do it in simple steps ?
Thanks
Related
I have a Firestore collection that I need to rename.
To do that I'll have to do two things. One, rename the collection, two, update my app (only web right now) to use the new collection name.
My problem is that if I just go ahead and do that, any user that has not refreshed the app won't be able to find the renamed collection.
So, my question is: Is there any best practice to handle this scenario?
I can think of a couple of options:
Somehow forcing a reload of the web apps immediately after renaming the collection.
Set a feature flag so that the web apps enter into maintenance mode while I update everything and then reload the web apps once the change is finished. Unfortunately the currently deployed web app doesn't have a maintenance mode to enable so this doesn't seem to be a valid solution.
However, I'd like to hear about other options. There might be some best practice that I'm missing. Moreover, I'm aware this is a problem that might be more general than just related to Firestore. For example when changing a REST API endpoint, so I guess there must be some tried and tested solutions out there.
I tried searching for best practices regarding this and couldn't find any.
Also, if I was consuming a REST API it would be easier to solve because I could change the DB and keep the DB unchanged. But given that Firestore gets consumed directly from the web app I don't have this benefit.
Locking out outdated clients is a common practice, but leads to a lesser user experience. It also requires that you have a mechanism for the clients to detect that they're outdated, which you don't seem to have.
The most common practice I know of is to perform dual writes to both the old and the new collection while clients are updating.
Can someone connect me with anyone from here who can help provide access to the Flutter navigation API as well as access keys?
I tried several routes, it’s been a couple of months and nothing yet.
Last time someone called me, I think from sales, but no follow up (two weeks already)
I’m not sure the person knew the SDK existed...
Usually, the connection starts from here: https://developer.here.com/contact-us. The HERE team is quite fast and responsive, so you should get a quick reply.
Help!
I’ve been trying to transfer an app for a month now to a client and he’s getting angry! The last box in App Store connect about the TestFlight builds won’t grt ticket, and I don’t know what to do. I’ve tried everything. All builds are gone, all info from localizations, I’ve made countless updates, everything. I contacted Apple support but they’ve just kept passing me to different levels of support so far. I don’t know what do to. Is there a way to manually transfer it? Like if I removed mine from sale, and uploaded it on the clients side? And help is appreciated, thanks!
for transferring your app to the diff account.
All the test flight build has to be deleted manually.
All the test details has to be wiped off.
All the App information has to be cleaned in the app information section.
But i could see that you didn’t deleted the test flight build properly. thats why you are getting this error. i succeed transferring my 2 application.
If I attempt to add a new SQL data model, a popup shows up explaining that the feature is locked and I must contact my administrator (myself). However, there is no further explanation found in the documentation on how to unlock this feature.
This is how AppMaker used to look back when it allowed me to add database connections:
This is how AppMaker looks now when starting a new app:
The App Maker engineers are doing crazy changes now and then. I believe their point of view is to make the platform better but this kind of things really annoys me and makes life harder, honestly.
I ran across this problem and find out that they are forcing admins to set up a default instance in the G Suite Admin console. You can read more about that here. You haven't completed that step and that is why you see what you are seeing. Although, it's crazy! What if I don't wanna do that?! But they are the product owners and they establish the rules so we have to suck it up and do what they want! Unless a bunch of people complain about it, they are not changing the behavior.
Fortunately, I was able to find a work around. So what we (you and me) are trying to do, is set up a custom sql database. Right now, that will only be available if you've already done what I described above. So the work around is to import an app that already has a custom sql database set up and then modify the Google Cloud SQL address. Look at the example below:
Here is the demo workaround app that I use. Download it to your machine, then import it as in the image above. I hope this helps!
I recently got into a project where I need to support for two mobile applications build using asp.net.
Can anybody share the jobs need to do in maintaining those projects ?
Thanks.
Nilesh
I think you may consider the following points while you are doing maintenance projects :
1) You should talk to your manager and make them understand that you are overloaded and you can't do effective work if everyone keeps bombarding you with requests which they want fulfilled immediately.
2) You should keep tracking on what you have done and how.
3) Keep backups regular basis of all the tasks you have completed.
4) Keep updating your manager on what task you are working and what you have understand and how you want to work/achieve this.
5) Ideally, all incoming requests should be entered into an issue tracker like JIRA or Mantis. Or at least mailed to the product owner, not you. And he/she should deal with all the complaints from the users too over "why is my request not ready yet?!", allowing you to focus on the development work.
Hope it helps you. :)