Something seems to have changed recently (early Nov 2014) in the way the example buttons work to start a Hangout On Air (HOA). https://developers.google.com/+/hangouts/button
I have been using this example code from the link above as a starting point to make a "Create a Hangout On Air" button on my website.
<script src="https://apis.google.com/js/platform.js" async defer></script>
<div id="placeholder-div3"></div>
<script>
gapi.hangout.render('placeholder-div3', {
'render': 'createhangout',
'hangout_type': 'onair',
'initial_apps': [{'app_id' : '184219133185', 'start_data' : 'dQw4w9WgXcQ', 'app_type' : 'ROOM_APP' }],
'widget_size': 175
});
</script>
The initial_apps line is supposed to cause the HOA to automatically start the Youtube hangouts app (the app_id) with a particular video (the start_data). A couple weeks ago this was working. Now it is not. The initial_apps parameter seems to have no effect on the initial start of my HOA.
Another change I have noticed is that when I press the Create a Hangout button, I am now taken to a Google+ page where I enter a name for the hangout and guests, and then I have to push another button to actually start the HOA. This extra button push was not around previously.
I don't particularly care about the Youtube app starting, but I do care about my own app starting with my own start_data.
Has something changed recently? Why is this not working?
UPDATE: As of 16-Nov-2014, this bug seems to be fixed.
Yeah I am facing the same problem.
My app also doesn't get loaded properly. Most of the times I get can't load app because the app is not communicating with the server.
I figured out that the Hangouts On Air button works as expected only when you add an 'invites' attribute with at least two people in the list. Not zero, not one. Two or more.
I feel like this is indeed broken. There should be means of passing initial_apps data without requiring that invitees be submitted in the button.
I had this same problem and John L's solution worked for me. It seems Google fixed this bug and it's now working like before so you don't need to have at least two people in the invites attribute anymore.
Related
I have an Elm app. A while ago I realized that my app was crashing locally when I used FontAwesome icons. I came to understand that it happened because I chose SVG icons and therefore FontAwesome was modifying the DOM. That conflicted with Elm's VDOM mechanism.
This was easy to fix--I migrated to the CSS version of FontAwesome that uses pseudo elements. Recently some users complained that the app in production freezes and they showed screenshots of states that were not matching the log data I had. It took a while until I realized that all these users had Google Translate automatically translated the page for them. Google Translate clearly alters the DOM, so I'm not surprised that it made Elm crash.
How can I prevent my Elm app from crashing? Is there a way to be notified if a 3rd party changes the DOM? So that I could even notify the user that they have an extension that interferes with the app.
I had the same problem as you and solved it by migrating to the Elm-FontAwesome library. Basically all you have to do is replace this syntax:
i [ Svga.class "fas fa-check" ] []
with this one:
Icon.viewIcon Icon.check
You can have a look to the example project for more details: https://github.com/Lattyware/elm-fontawesome-example
Have a look here - How we made Elm and Google Translate work together.
Their approach is to hijack the Elm replaceData method that is called by Elm during dom updates using the function below. You would run this just before giving Elm control of the dom.
HTMLFontElement.prototype.replaceData =
function replaceData(_0, _1, string) {
this.parentNode.replaceChild(
document.createTextNode(string),
this
);
};
Apparently, "Google Translate replaces every text node in the DOM with a tag containing at least one more tag – one for each sentence". For example:
<span>Insurello. Rätt ersättning till alla</span>
is translated into
<span><font><font>Insurello. </font><font>The right compensation for everyone</font></font></span>
This method avoids attempting to edit the span and instead replace it with a new one. Once the node is added, Google Translate will translate that text.
I don't know about preventing the crashes, but I think you should be able to register changes to the DOM with the current mutation observer API.
Before that were several deprecated mutation events like DOMSubtreeModified that could also help, but well they are deprecated.
This problem is very closely linked to that of Google Maps or Google Places Autocomplete in Elm. The solution I've used in the past is to provide a childless div with an id I can point to from JavaScript.
Because the div is childless, Elm does not look under the hood to check whether it has changed internally.
Check out this blog post or google "maps in elm" for instructions on how to do this
-- EDIT --
Ive read the question better and this will probably not work for Google translate issues as it changes all text in the entire DOM. Ill leave it here incase the question brings otger people who have more regular problems caused when a 3rd party changes the DOM
We've been using the as yet un-deprecated "Start a Hangout on Air" button:
https://developers.google.com/+/hangouts/button
to start hangouts on air on our site http://agileventures.org for several years now. Full source code at http://github.com/AgileVentures/WebsiteOne
In the last 24 hours, clicking those buttons now redirects to instructions to manually start a youtube live event:
https://support.google.com/youtube/answer/7083786?visit_id=1-636118907663120157-3101666316&p=live_hoa&hl=en&rd=1
This is a problem as manually started events will not create the hangout app that lets our community know an event is starting and provides us with important telemetry on events.
There is unfortunately no documentation in the youtube live streaming API about how to create a button that will create a youtube live streaming event, or load a plugin into that event:
https://developers.google.com/youtube/v3/live/docs/
We need some code similar to that provided by the hangouts api, e.g.
<script src="https://apis.google.com/js/platform.js" async defer>
</script>
<div class="g-hangout" data-render="createhangout"
data-initial_apps="[{ app_id : '123456789012', start_data : 'dQw4w9WgXcQ', 'app_type' : 'ROOM_APP' }]">
</div>
but that will work with the new youtube streaming api. Any ideas?
The YouTube live documentation talks about being able to create a broadcast, but it seems to be only for custom "streaming" broadcasts and not hangouts:
https://developers.google.com/youtube/v3/live/docs/liveBroadcasts/insert
The new events page allows us to select the "quick" type, which creates a hangout on air (https://www.youtube.com/my_live_events?action_create_live_event=1) so we can create HOAs manually, but not programmatically? We would very much appreciate clarity from Google on this.
It seems that support for Hangout on Air Buttons, creation of HOAs via API has been dropped no?
Note that Google is specifically requesting support questions for the Youtube LiveStream API are posted to StackOverflow:
https://developers.google.com/youtube/v3/live/support
The functionality all started working again after a 3 week break. We're not sure if Google changed anything. There were no changes on our end. Buttons for starting HOA's have been stable now for the last two months or so ...
Getting this error again and again after adding image and hitting Save button. "Your In-App Purchase information could not be saved. Try again. If the problem persists, contact us."
I don't know why this was rejected as an edit. Anyway:
No, this is not a duplicate. This is about In App Purchases while the question you mentioned is about App status.
I was facing the same problem today, and it seems other people too.
What I tried and didn't work (so please don't put this as a possible answer): 1- I used google chrome + Safari on Mac OS 10.12, no chance. Then I tried private mode (same as delete cookies and history), no chance.
2- I switched to windows 7 computer, chrome + firefox (never used before), no chance.
3- I used Safari on iPad Mini with iOS10, no chance.
4- When posting a new IAP with an attached screenshot image, the save button will load forever and nothing will be saved.
5- I contacted Apple about the problem and gave all details. I am waiting for the solution.
Edit : Finally, it is working again (October 7th, 8am GMT). I don't know wether contacting Apple solved this or it was solved for every one. I just uploaded the screenshot and saved the In App Purchase, and I am able to submit the app for review.
If it still doesn't work for you, just contact Apple support with the link provided in the error message, and be patient (try to work in another thing, drink a coffee, or go to shopping :) )
Eventually today i got the success when i had tried from different system,i used the screenshot from iphone5s simulator in 100% resolution and got the success.
But same-thing,i had also tried before putting up this question.
So that means it might be error from apple server as sometimes it just not works.
PFA for screenshot i used:-
If you are resubmitting (for example, after a previous rejection), it seems like this can be caused by adding additional in app purchases.
Our app binary was rejected, we uploaded a new one and while we were at it we added an additional in app purchase to the submission and some extra text to the app review information. All other in app purchases previously submitted remained "In Review" so we were literally just adding in another to the submission.
We got a 500 Internal Server Error when clicking submit (verified using FireFox dev tools). We tried Safari, Chrome, Firefox on Mac and PC - all up-to-date. Same behaviour.
We tried removing the extra new in-app purchase (and cut down the extra review text a little) from the submission and it immediately went through without a hitch. YMMV, but worth checking.
First time trying to create a Facebook app. Browsed to https://developers.facebook.com/apps and it had a link for to register before creating a link where you just accept the T&C's. Now it says, "Create an app to start..." But there is no button to click to create app.
I was having this SAME exact problem just now. I have a verified personal account (email and credit card) and I couldn't see the button. This is what I was getting:
I was at my wits end after 5 hours of reading similar questions and started pulling my eyelashes out...because I have no hair. I tried:
Turning off AdBlock
Testing in multiple browsers and OS'
Inspecting the area with Chrome Inspector...which turned up an empty #DeveleperAppDashHeader div
Praying to the rain gods
Eventually, I became so desperate that I started typing random urls, and this one, by the Odin's Raven, worked: http://developers.facebook.com/setup
It creates a popup window that will let you get the ball rolling. Let me know if this worked, because I am damn near ready to hump my chair with excitement.
Also, I suspect that this is a bug...because if I can create an App using this link but not through the dev dashboard, then something is up.
Here is an explanation about how to create a new app - http://ftutorials.com/create-facebook-app/
First you should check that you are not trying to create a new application from business account. You can create new app only from a facebook account of a real user.
Also there is some facebook bug, that after you click on "Create app", nothing happens, but your app is created.
I was using an iframe share button solution to be able to share products or posts on facebook. I used this systeme wich worked great on about 10 different websites but this week, they all ended up no working.
I read I should get an appId for each website and use Asynchroneous SDK, which I did, and followed steps to get it to work:
Load the SDK with appId authentification.
Load jQuery if needed (some buttons require it).
Add button code were desired.
I can see the SDK is loaded in <div id="fb-root"></div> but the share button never appears on the page and it is not a layout issue. I have tried several different buttons but they all seam to never make it to the user.
I read a lot of posts about the issue but each one was magically solved on Jully 22nd... not mine. I need help implementing this first button as I need to fix many websites afterwards. Thx!
When doing a fresh implementation of FB btns I ended up going here:
https://developers.facebook.com/tools/debug
to force FB to crowl the pages I was working on at the moment.
This proved usedful in getting immediate feedback on how things were working out.