Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

[RESOLVED] Graphics 2.0 and Enterprise
Started by borderleap Oct 28 2013 08:06 AM

13 replies to this topic
graphics enterprise
[TOPIC CONTROLS]
This topic has been archived. This means that you cannot reply to this topic.
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

borderleap

[GLOBAL: userInfoPane.html]
borderleap
  • Contributor

  • 400 posts
  • Corona SDK

We've just started using Enterprise recently and I'm curious if anyone's been using the Graphics 2.0 engine inside an Enterprise setup?  (or if this is possible yet)

 

Thanks,

Nate



[TOPIC: post.html]
#2

fitnate

[GLOBAL: userInfoPane.html]
fitnate
  • Observer

  • 2 posts
  • Enterprise

Anyone tried this?  Anyone from Corona staff able to answer?  Thanks!



[TOPIC: post.html]
#3

mpappas

[GLOBAL: userInfoPane.html]
mpappas
  • Contributor

  • 527 posts
  • Enterprise

I don't think it's possible until they release an enterprise version with 2.0 in it.

 

I asked something like this a few days ago on the enterprise forum, as I'm having trouble accessing coronas opengl buffers from enterprise:

 

http://forums.coronalabs.com/topic/40824-opengl-11-vs-20-and-stuff/

 

But no response at all... btw, if you've been able to access coronas gl buffers in enterprise, feel free to post on that topic :)



[TOPIC: post.html]
#4

Bryan01

[GLOBAL: userInfoPane.html]
Bryan01
  • Enthusiast

  • 95 posts
  • Corona Staff

The daily enterprise builds are now linked to on the daily Graphics 2.0 page. There are a couple frameworks that should be added to the projects to successfully build: CoreVideo.framework, and GLKit.framework.

 

http://developer.coronalabs.com/downloads/enterprise-graphics-daily-builds



[TOPIC: post.html]
#5

borderleap

[GLOBAL: userInfoPane.html]
borderleap
  • Contributor

  • 400 posts
  • Corona SDK

Excellent - thanks Bryan!  Going to try this out now...



[TOPIC: post.html]
#6

borderleap

[GLOBAL: userInfoPane.html]
borderleap
  • Contributor

  • 400 posts
  • Corona SDK

Whatever you guys did to the Facebook plugin between builds 2035 and 2036 really caused FB to break on our end.  We had a login() and request() call working flawlessly and build 2036 caused it to completely break on us.   The app would repeatedly try to access permissions with the native FB app and then return to our app, then back to FB app and back to our app and then to the FB web popup...   and then break.  
 

Wish I had more time to share more details but we're hammering away at a hackathon and just lost a couple hours dealing with this.  We've reverted back to 2035 and all is good.  Wanted to let you know!!  ;)



[TOPIC: post.html]
#7

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 25,925 posts
  • Enterprise

Hey @borderleap, we made changes to facebook.login() in 2036 to satisfy a Facebook requirement to avoid using webViews for logging in.  It had to do with the requesting of extended permissions on a second pass.   We should be handling that correctly now and you should just be able to call facebook.login() and pass in the privs you want and not have to do secondary logins.

 

I'll get the engineer working on this to look at this thread, but I need to know what login workflow you are using.

 

Thanks

Rob



[TOPIC: post.html]
#8

walter

[GLOBAL: userInfoPane.html]
walter
  • Moderator

  • 726 posts
  • Alumni

To add to what Rob said, the change between 2035 and 2036 mirrors the change we did in the 1.0 daily builds. These satisfy new requirements that Facebook has imposed.



[TOPIC: post.html]
#9

borderleap

[GLOBAL: userInfoPane.html]
borderleap
  • Contributor

  • 400 posts
  • Corona SDK

I changed my login() call to request these permissions:

{"email","user_birthday","publish_actions"}

and after a successful login, I'm now doing a facebook.request() call:

facebook.request("me?fields=id,email,name,first_name,last_name,gender,birthday,picture.width(85).type(square),locale")

The app now frantically goes back to the native Facebook app repeatedly...  this is using the latest Enterprise/Graphics 2.0 build, 2057.

 

Any idea why?



[TOPIC: post.html]
#10

fitnate

[GLOBAL: userInfoPane.html]
fitnate
  • Observer

  • 2 posts
  • Enterprise

Testing this further..  I removed the permissions except for publish_actions.   Testing in iOS Simulator and on an actual iPad.   Login process starts when facebook.login() is called, jumps over to the native Facebook app to authenticate (I thought using native iOS login wasn't supposed to do this?), then returns to the app...

 

What's weird is at this point it hangs for like 30-45 seconds before it then AGAIN jumps this time out of the app over to a web view with the facebook.com auth screen.



[TOPIC: post.html]
#11

borderleap

[GLOBAL: userInfoPane.html]
borderleap
  • Contributor

  • 400 posts
  • Corona SDK

Sorry, "fitnate" is me :)  I have two Corona accounts - one for Pro and one for Enterprise with a startup I'm working with.



[TOPIC: post.html]
#12

dchan

[GLOBAL: userInfoPane.html]
dchan
  • Contributor

  • 360 posts
  • Corona Staff

Facebook has 3 login screens on iOS for the following cases:

1) when the Facebook app is installed

2) when the user is logged in via the phone and the facebook app is not installed

3) when the user isn't logged in via the phone and the facebook app is not installed.

https://developers.facebook.com/docs/ios/login/

 

Also we're looking into the issue right now.  A few questions though,

1) what version of iOS are you running

2) what version of the facebook app are you running

 

Thanks.



[TOPIC: post.html]
#13

borderleap

[GLOBAL: userInfoPane.html]
borderleap
  • Contributor

  • 400 posts
  • Corona SDK

Hi dchan, I'm testing this on iOS 7.0.3 and on the device, Facebook 6.7.1

 

Nate



[TOPIC: post.html]
#14

borderleap

[GLOBAL: userInfoPane.html]
borderleap
  • Contributor

  • 400 posts
  • Corona SDK

And I'm using the latest Corona Enterprise + Graphics 2.0 daily build (2057)




[topic_controls]
[/topic_controls]