here is my code :
https://github.com/jonny720/do-here-client/tree/master/do-here
i took the map component code from here :
https://github.com/dapriett/nativescript-google-maps-sdk/tree/master/ng-demo/app/map
the map component should display the google maps but nothing is shown.
*i installed google maps sdk, and setup the api key in the android platform.
its the first time i'm working with api in my app.
can someone light my eyes and tell me what is the problem?
The api key is missing and you should register custom element in main.ts file, and the 2 files to copy from the nativescript-google-map module were missing from your app folder
and as well as the key too.
I forked your repo and update the app, also created a .gitignore file to exclude unnecessary files and folder from repo.
I tested and it works fine.
You will have to update these files with your appropriate Google API key
> do-here/app/main.ts
> do-here/app/App_Resources/Android/values/nativescript_google_maps_api.xml
> do-here/app/App_Resources/Android/src/main/res/values/nativescript_google_maps_api.xml
and update this file to redirect all unauthorized access back to login page, changed it to test the map page
do-here/app/#shared/services/auth-guard.service.ts
ok first thank you a lot KielSoft
i solved it by typing in the cli :
tns tun android --clean
Related
New to Amplify. Following the tutorial on AWS and everything looks good.
Now I want to add a simple html file, called abc.html, just some basic html code for a test. But when I try to visit the url: https://www.yourdomain.com/abc.html, it redirects the url to https://www.yourdomain.com/abc/. So it basically doesn't recognize there is a file called abc.html. How can I add new files to Amplify?
From Amplify console, everything looks OK. It responded to the git push. Provision, build, deploy, verify are all green. It just can't recognize the new added file. Any suggestions?
I figure out the problem. Post it here in case people have the same problem.
It's a bug in Amplify web framework. If you access the file before the branch gets built and deployed, the web framework can't find the file. So it will show 404 page and record the url as 404. Later, even if you build and deploy the file through Amplify, the web framework still remembers the 404 response to the specific url. It won't refresh. That's why if you add a html file to the repo and access it before Amplify finishes deployment, the file is forever treated as not exist.
I have added universal link support for an app. The following are added
aasa file is added at the root of the Website URL.
The entitlements file contains the appropriate URL
When the device is connected and app is installed using Xcode in Debug mode, the Universal linking works (Tapping on a link present in Mail opens the app).
However, when the app is archived and installable is created, tapping on the link opens the app in Safari Browser instead of opening the installed app.
Am I missing any other detail specifically while creating an archived installable ?
Resolved:
Add the .entitlements file in the Build Phases -> Copy Bundle Resources option.
While exporting validate that the entitlement for Associated Domain is available. If not, then turn the Capability On/Off, Close Xcode and reopen and then retry. Once it is available, then export the Archive.
Lastly, set a valid path "/somepath" instead of simply "*" in the aasa file.
Making the above changes helped to get it working.
This Meteor web browser site uses the package mrgalaxy:stripe, The first instruction is to
put App.accessRule('https://*.stripe.com/*'); in a client side file mobile-config.js.
Which when done exactly, causes the browser to issue an error:
Uncaught ReferenceError: App is not defined
I looked in Meteor doc but could not figure it out.
Any idea how to fix this? Thanks
You should have that file in the root of your app, not inside your client folder.
From mrgalaxy:stripe documentation:
In order for Stripe.js to be loaded directly on iOS and Android a new rule needs to be created in your mobile-config.js located in the root of your project. Create the new file if it doesn't already exist and insert the line below.
This is necessary for mobile builds to access external URLs. If you're building a mobile app from Meteor, you'll need to add additional configuration info to that mobile-config.js file before deploying. See https://docs.meteor.com/api/mobile-config.html
I have a hosted site on firebase which I am not using anymore. I still want to keep the project but want to remove the hosted site. Is there any way to do this or do I just need to upload an empty directory. Doesn't seem to be an option in the UI
It can be deleted.
Run firebase hosting:disable through the firebase-tools CLI first.
Go to Firebase Console and select Hosting from the menu of the left.
You will see the deployed project with a list of your historical actions like Deployed, disabled, etc.
Only after you have disabled the site, the "three vertical dots" menu will be available for you to choose the action to delete the deployment.
If you have multiple site hosted in same project, then use -s flag to specify the site you want to disable.
firebase hosting:disable -s yoursitename
You don't need to upload empty directory.
Just open your project's root directory and enter the following command
firebase hosting:disable
CLI Response :
$ firebase hosting:disable
? Are you sure you want to disable Firebase Hosting for the site xyz
This will immediately make your site inaccessible! Yes
✔ Hosting has been disabled for xyz. Deploy a new version
to re-enable.
This will instantly disable running website also adds a Disabled status in release history. Tested on firebase CLI version 9.20.0
It's a bit hidden, but here are the steps:
Go to the Firebase Hosting console for your project, you will see your domain.
Hover over your domain. There's an overflow menu (⋮ three vertical dots) on the right.
From the overflow menu select Delete Domain
[Update]
For multiple site hosted !! use command
firebase hosting:disable --project yoursitename
for me it work!! Can your try?
You can use the following command:
firebase hosting:disable -s <firebase_project_name>
replace <firebase_project_name> with the name of your firebase project. This allows you to unsubscribe from the current project and place it in disable mode and you cannot receive traffic from the published web page. When you want to re-enable it, you can do it from the visual platform. I leave an image attached so that you can be guided.
Manually
You can easily go to the console, and click on the 3 vertical dots and delete the site.
Using CLI
Disable only
Stops serving Firebase Hosting traffic for the active Firebase
project.
Your project's Hosting URL will display a "Site Not Found" message
after running this command.
If you want to disable, as the other answers are saying use this command:
firebase hosting:disable
If you're using multi-sites, you have to specify the project name:
firebase hosting:disable --project yoursitename
Delete forever
Deletes the specified Hosting site.
Deleting a site is a permanent action. If you delete a site, Firebase doesn't maintain records of deployed files or deployment history, and the site cannot be reactivated by you or anyone else.
(Optional) Skip the confirmation prompt by passing the following flags: -f or --force
To delete this site (similar to when you go to the console > delete manually) run this command:
firebase hosting:sites:delete yoursitename -f
Be careful when using the -f, but if you're running this as a script command, it might be required.
I spent too much time on this and hopefully this can be helpful. I did deploy my stuff using firebase deploy however I was not able to see in on the firebase console. When I tried firebase hosting:disable I got this Error: HTTP Error: 400, Invalid project ID specified.
The steps below helped me delete my project.
To find the project, you have to get the output of firebase
deploy which will have a console url that looks like this:
Project Console:
https://console.firebase.google.com/project/<your-project-id>/overview.
Follow this link and go to project settings. You should be able to
delete your project in there.
I had to spend several hours removing the default website on Firebase hosting.
The way that I found was :
Enter "firebase init database" in Terminal. It initialize all websites including the default one so that you can set up a new one.
I hope it helps you.
As of now there is no proper way to bulk delete all the previous deployments in a project.
However the best thing you can do is to empty the firebase hosting folder and then deploy it using firebase deploy
This option has been given as a feature request to firebase. Lets hope its get implemented soon :)
1.Sign in to Firebase, then open your project.
2.Click the Settings icon near project Overview button, then select Project settings.
3.In the Your apps card, select the app that you want to delete.
4.Find the Delete Project button from bottom of the page , click Delete Project.
5.Check the points , then click Remove app permanently.
As Apple requested to use https instead of http for distributing the IPAs over the air, I tried to use dropbox. I followed this solution Enterprise app deployment doesn't work on iOS 7.1 but I'm getting this error:
"Cannot connect to dl.dropboxusercontent.com"
when trying to install the plist through this link: <a href="itms-services://?action=download-manifest&url=https://dl.dropboxusercontent.com/s/56ny312cwdacho7/xxxxx.plist> Install </a>
Thanks in advance.
NOTE : Shared links don’t render HTML content in a web browser
Refer https://www.dropbox.com/help/desktop-web/force-download
Check question
How to force render a file in a browser
EDIT : Reason is you will need to change link url and reupload it :
replace www.dropbox.com with dl.dropboxusercontent.com inall links
Reupload by making changes in link which are in html and plist file again.
Thats it. Enjoy
TOTAL SOLUTION
Needed file for distribution using example link are given below :
Build your app from xcode using Build and Archive option. Upload your ipa file to Dropbox. And get public link for the ipa.
Note : replace www.dropbox.com with dl.dropboxusercontent.com in the link.
Download the manifest.plist - edit the line #14 with the public link of your ipa . Modify other keys as well (bundle-identifier, bundle-version, title) .
Upload the modified manifest.plist to Dropbox and get its public link.
Download the index.html - edit url param at line #8 with public link of your manifest.plist
Hosting using Github. How that can be achieved is explained in following steps
Create a new project.
Add index.html as we will be hosting a site in Github Pages. Note
html file with other name will not be valid as it should always be
with index name.
Now go to project settings. Traverse through Github Pages
Under source tab select master-branch and click on save
Traverse back Github Pages you will see site will be published
Now you have Download link like https://paresh-navadiya.github.io/install.html/
Refer How to distribute using DropBox by #
oldman's answer and Distribute your iPhone/iPad adhoc builds Over The Air using DropBox
It working 100% percent.
Have a nice day to all :)
I had exactly the same issue. Firstly I tried putting all of my files in the public folder of my dropbox account. It still didn't work but I noticed with modifying my plist file I had overwritten the closing "</string>" XML tag for the ipa file itself. Once I added that back in it all worked. So whether it would have worked without moving to the public folder I do not know. I haven't tried because I have the result I desire for my users.
I faced the similar issue with dropbox few days back, saying cannot connect to dl.dropboxusercontent.com, what I did is deleting the sharable link which I created earlier and created a new sharable link for both plist and ipa files. And I updated these links in plist and html page. I don't know what was wrong with my old sharable links. Hope this answer might be helpful for someone.
Happy coding.
As already pointed out in a similar reply here, if the PLIST file is malformed, this error will appear.
In my case, I forgot the fact that the ampersand ("&") charcater is forbidden in XML, and the name of my app contained "&" in it, so I had to replace the & with & in the containing the name and everything worked.