Yesterday I configured Sign in with Google on Android. Today is more of the same but in iOS land.
From the app directory I ran open ios/Runner.xcworkspace to open the iOS project in Xcode. Then in Xcode I selected "Runner" under "Project navigator"in the left sidebar followed by "Runner" under "Targets" in the main content area. Here I set "Bundle identifier" to app.birb.
Using the development Firebase project from yesterday, I added a new iOS app using the same bundle ID.
Firebase then prompted me to download a GoogleService-Info.plist file.
Once downloaded, I dragged the plist file into the Xcode "project navigation" sidebar within the "Runner" directory next to Info.plist. By dragging it into Xcode, it gets registered for inclusion during builds. There isn't any sensitive information in the file but for an open source project it will need to be different for every developer so I'm adding it to .gitignore.
I then skipped step three "add Firebase SDK" and step four "add initialization code".
There is one important change to ios/Runner/Info.plist: configuring a CFBundleURLSchemes. The value can be copied from the GoogleServiceInfo.plist file. I would like to not hard code this but I currently don't have a better alternative.
<array><dict><key>CFBundleTypeRole</key><string>Editor</string><key>CFBundleURLSchemes</key><array><!-- Copied from GoogleServices-Info.plist key REVERSED_CLIENT_ID --><string>com.googleusercontent.apps.483795507272-cavro2su6d78ldumt6003lo2krdrb2dd</string></array></dict></array>
Starting the app should give Firebase the all set signal.
And the Sign in with Google button still doesn't do anything but maybe tomorrow it really will.
* In the web interface new mentions are only replies if they start with @screen_name. By pushing @screen_name further along in the string your followers who do not follow @screen_name will still see the status.
"Storytlr is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation."
I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal. While I love Drupal and FeedAPI I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions.
Assumptions: LAMP stack installed and running.Domain setup for a directory.MySQL database and user ready to go.Lets get started! Get the code: wget http://storytlr.googlecode.com/files/storytlr-0.9.2.tgz
tar -xvzf storytlr-0.9.2.tgzYou can find out the latest stable release on Storytlr's downloads page.
Import the database:
Within protected/install is database.sql. Import this into your empt…
Update: I now recommend you install Google Chrome and disable the built in Browser as it supports encrypting all synced data.
After picking up a gorgeous Galaxy Nexus yesterday I was running into an issue where my browser data wasn't syncing to the phone. After a little Googling I found this is commonly caused by having all of my synced Chrome data encrypted instead of the default of only encrypting the passwords. These are the steps I went through to get my dat syncing again without losing any of it. The exact error I was getting was "Sync is currently experiencing problems. It will be back shortly."
In Google Chrome open the personal stuff settings page by clicking this link or by opening the wrench menu, and click on "signed in with firstname.lastname@example.org". Hit "disconnect your Google Account" to temporarily disable syncing from your browser.
Visit the Google Dashboard and "Stop sync and delete data from Google". I waited until the stored dat…