I have a monolith jhispter app and an ionic-jhipster app both working fine together (Thanks to Matt Raible and JHipster team). And I'm not sure if my problem has anything to do with JHipster.
Since I'm working on windows, I thought maybe I'd be better to use Ionic Pro cloud services to build my app for ios and Android. Please correct me if I'm wrong.
Here is the process I went through:
1-I added my Ionic app on GitHub. So, I'm using GitHub as my Source Control
2-I used "ionic ssh setup" command to create SSH public/private keys and I believe it took care of generating the keys and putting them in the right place I guess I didn't have to generate the SSH keys since it could work just by my user name and password too. Is that right?
3-I went to my app's folder and used "ionic link" to link my existing app to my Ionic Pro dashboard
4-In answer to existing app or new app (which was not clear to me what it's asking for), I chose new app since GaëlMarziou helped me in the comments section to understand there should be an app already created in my Ionic Pro so I can link my local app to it. It took me a while so I understood this prompt is asking about the dashboard app not my local app. I chose "new" since it was the first time I was using my Ionic Pro account and I had no app on it.
5-Then it asked about the source control and I chose GitHub and provided the credentials
6-Then it showed me a list of my repositories on GitHub so I can choose one. But before I do anything it just jumped out with no error/success messages. And I considered it done since I had the same names for my app and GitHub repository and I thought maybe it was smart enough to find the correct repository.
Now, I can see an app in my Ionic Pro dashboard but the build and commit history is empty and it looks like the app is not linked yet.
I tried "git push origin master" to build my app when I was in my Ionic app folder. I assume "origin" would work for any git repository, am I right? It tells me everything is up-to-date and nothing happens in my Ionic Pro dashboard.
Related
I have completed an application that works fine in development env, both on android emulator and android phone.
I created a keystore, added INTERNET_PERMISSION to my manifest and followed the guide to release pretty much perfectly.
However, when I download the release app from the play store (it is in internal testing), the login API (and presumably the other APIs) do not work and infinitely load.
What did I miss?
The IOS Application is working perfectly in Testflight.
Assuming that you are using firebase.
After deployment to playstore.
Go to Play Console → Open App → Setup (Left panel) → App Integrity
you should be able to see something like this.
add the SHA-1 and SHA-256 fingerprint to the firebase project in firebase console and it should work after that.
Open Firebase Console → Open Project → Project Settings → General, scroll to very last and add these certificates.
UPDATE:
You need to get the new google-services.json from firebase, add it to your app, make new build and re-deploy to playstore with a new version for this to work.
I'm evaluating appflow as it'd be very useful for our project and would be keen to get one of the paid plans.
However, I don't seem to be able to get the basic live deployments working with my Ionic/Angular/Capacitor app, and I'm a bit at a loss as to how to troubleshoot.
I have followed the docs and installed the SDK in my app.
I can see the app id, channel name (Production) and update method (auto) in string.xml and info.plist.
I have successfully built the app in appflow (web build), and I can see on the deployments screen my build assigned to the production channel of type 'Live Update'.
I'm not seeing changes on device after the splash screen, so I've put together a screen using the 'Deploy' plugin to show me what version is installed, and if updates are available.
import { Deploy } from 'cordova-plugin-ionic/dist/ngx';
...
private async loadDeployInfo()
{
const info = await this.deploy.getCurrentVersion();
if (info) {
this.liveUpdateId = info.buildId;
}
const updateCheck = await this.deploy.checkForUpdate();
console.log(updateCheck);
if (updateCheck.available) {
this.updateAvailable = updateCheck.build;
}
}
I call the above 'loadDeployInfo()' when my view loads and display out the build Id and whether an update is available. Neither show up anything when testing on device. I'm using capacitor, so running locally involves running ngx cap commands and opening android studio, which is not a tool I know how to get debug information out of, but I'm not seeing any red in the console as it's running.
I'm a bit stuck. I'm keen to use app flow, but I'm not seeing basic live updates take effect and there's not much documentation on troubleshooting.
From Ionic forum posts I've managed to piece things together. The long and short of it is that the 'ionic deploy add' command doesn't seem to perform all the required configuration to make AppFlow work, at least on a Ionic/Angular/Capacitor based app.
Having followed the steps in the quick start guide here: https://ionic.io/docs/appflow/deploy/api
I needed to do the following:
To get Appflow going on Android, find 'strings.xml' in your Capacitor app's 'Android' folder and add the following if they are missing:
<string name="ionic_max_versions">2</string>
<string name="ionic_update_api">https://api.ionicjs.com</string>
<string name="ionic_min_background_duration">30</string>
For iOS, find your Capacitor apps 'ios' folder and look for 'info.plist'. Here you may find existing entries that look like they are coded to variables:
<key>IonApi</key>
<string>$UPDATE_API</string>
<key>IonMaxVersions</key>
<string>$MAX_STORE</string>
<key>IonMinBackgroundDuration</key>
<string>$MIN_BACKGROUND_DURATION</string>
Swap these $ variables for hard coded values:
<key>IonApi</key>
<string>https://api.ionicjs.com</string>
<key>IonMaxVersions</key>
<string>2</string>
<key>IonMinBackgroundDuration</key>
<string>30</string>
Update:
I logged a ticket on the git repo for the CLI, and they've updated it, so it may hopefully work for you without the above (make sure you've the latest ionic CLI).
Problem:
I ve a problem for long time, where the smarthome app I created with Actions SDK doesnt show up in the Google Assistant app under home control as a test app.
I tried 3 different accounts, looked for being signed in with the same account, started from scratch but nothing helped!
Can you please help to solve this, since it is pretty bad that I cant test the final User oAuth flow from the Google assistant app.
This is BLOCKING me from continuing at all and also make me feel that Google Home is not that production ready.
Iam developing the smarthome app action for a worldwide known opensource project and a lot of users ask for Google Home. I have the implementation almost finished and it stucked at this not showing up in the assistant app. So I cant test and the community cant test either!
This is from my point of view, not good for Google and the launch of Google Home. I had many support tickets open, but still no solution. Hopefully the developers feel responsible and can help.
Environment:
MacBookAir: Mac OS X 10.12.15
Browser: Chrome, Version 59.0.3071.115 (64Bit)
Android Smartphone (Starting from Android v6)
Framework: Actions SDK (gactions)
Steps to reproduce:
Created a new project under
https://console.actions.google.com/
Added Actions SDK to my project and run these commands:
./gactions update --action_package action.json --project
<project-id>
./gactions --verbose test --action_package
action.json --project <project-id>
Added all needed App information and the Account Linking information
Clicked on TEST (next to SUBMIT FOR REVIEW) Button
Result:
I cant use the Simulator, cause when I type "Talk to ", I always get this ErrorMessage: "Sorry, this action is not available in simulation".
If I open the Google Assistant on an Android device and go to "Home Control" to see my test smarthome app, it doesnt occur in the list with brackets etc. like [test ...]. It is not there at all!
I found other devs having the same problem like me over here:
https://github.com/actions-on-google/actionssdk-smart-home-nodejs/issues/1
Here you have my command in the terminal to deploy the smarthome app via gactions command:
./gactions --verbose test --action_package action.json --project <project-id>
Checking for updates...
Successfully fetched update metadata
Finished checking for updates -- no updates available
Pushing the app for the Assistant for testing...
POST /v2/users/me/previews/<project- id>:updateFromAgentDraft?updateMask=previewActionPackage.actionPackage.actions%2CpreviewActionPackage.actionPackage.conversations%2CpreviewActionPackage.actionPackage.types%2CpreviewActionPackage.startTimestamp%2CpreviewActionPackage.endTimestamp HTTP/1.1
Host: actions.googleapis.com
User-Agent: Gactions-CLI/2.0.7 (darwin; amd64; stable/6f4c996f8ee63dc5760c7728f674abe37bfe5fc4)
Content-Length: 369
Content-Type: application/json
Accept-Encoding: gzip
{"name":"users/me/previews/<project-id>","previewActionPackage": {"actionPackage":{"actions":[{"deviceControl":{},"fulfillment":{"conversationName":"automation"},"name":"actions.devices"}],"conversations":{"automation":{"name":"automation","url":"https://MY-GOOGLE-CLOUDFUNCTION-URL"}}},"name":"users/me/previews/<project-id>"}}
Reading credentials from: creds.data
Successfully pushed the app for the Assistant for testing
Your app for the Assistant for project <project-id> is now ready for testing on Actions on Google enabled devices or the Actions Web Simulator at https://console.actions.google.com/project/<project-id>/simulator/
I am faced with the problem as you are. I have sent email to Smart Home team, but they just explained:
"Smart Home Apps not showing in the list of Apps under the Home Control section on the Google Home App is a known issue and we're currently looking into it. I will reach out to you as soon as I have an update on that."
Unfortunately, I do not receive any feedback so far, even I have opened many support tickets.
By the way, the offcial document has updated twice(July 14,2017 and July 25,2017). But it still now not works, I do not know what does it mean! It is very disappointed.
This bug has recently been fixed, so all users should now be able to see their test devices in the Google Home app.
I tried to follow this article on MSDN magazine enter link description here to add iOS push notifications. However the sample code they provide enter link description here is outdated(using VS2013). I tried to migrate the project to VS2015 by following enter link description here but still cannot get it to work.
Can anyone provide a working sample code in VS2015? Thanks!
You need to configure the notification hub to send notifications to your iOS app.
Here is a sample how to do this in step by step walk-through:
https://azure.microsoft.com/en-us/documentation/articles/notification-hubs-ios-get-started/
Hope this helps.
I've updated the sample to Visual Studio 2015 in my fork: https://github.com/ggailey777/mobile-services-samples/tree/master/CordovaNotificationsArticle
To get it to work, I also needed to add the Whitelist plugin, which is now a requirement to access remote services from a Cordova app.
I am waiting to merge it back into the upstream fork until after I can get it tested on iOS (it does work now on Android). As mostafa points out, you do also need to follow the steps to configure push notification for iOS, which includes doing a bunch of stuff in Xcode on the Mac.
I have installed the Titanium Developer 1.2.2 form my login account (on Mac system) and have done one demo project. I was able to see that working in the iPhone simulator. Now if I switch user and login to another account to run Titanium Developer there, it downloads and runs there but I am unable to launch any project there. The SDK Version simply shows as 'loading...'.
As a work around I opened a terminal window and typed sudo abhilash (assuming my login name is 'abhilash') and entered password and launched the Titanium from command line. It opened my instance of titanium and detected the SDK version properly as 4.2 and when I click launch in simulator, it throws the following error
Now how do I make it working for the second user account? I have triend re-installing the xcode and titanium from the second user's account but no success :(
Kindly help!!
It doesn't answer your question specifically but this post was helpful for me in enabling Titanium to be used across different user accounts. I suspect you may have already tried this since I couldn't even get Titanium to open in another user account
http://developer.appcelerator.com/question/21121/titanium-crashing-on-startup-on-mac
the other thing to try is to create a new project in the new users account and then copy the contents of the "Resources" directory into the newly created project. I found this also fixed an issue of opening an old project.