iOS Question Hosted mac builder thinks its release mode after first project

Simon Smith

Active Member
Licensed User
Hello
I can't run any apps on B4i in Debug mode, I have tried removing files from c:\b4i\keys. Maybe I should uninstall and reinstall. It complains about provisioning profiles but im simply going to the b4ibridge on my iPhone connected via IP in debug mode. I can't see anywhere to turn release mode off. I just press debug and play. Any ideas?

Any application. Thanks heaps, Simon.
 

Attachments

  • help.png
    help.png
    38.3 KB · Views: 117

Simon Smith

Active Member
Licensed User
Hi thanks but I want it to go back the way it was, without provisioning profiles, simply debug on the device. It is always building a release version and never used to. Is there not a way to just go back to the settings since I built my first proper provisioning App. I know how to make a proper App, I want to just debug away.
 
Upvote 0

Simon Smith

Active Member
Licensed User
Ok provision file working, port working (it definitely is as it reacts on the other end. On running on the macbuilder alone "java -jar B4iBuildServer.jar" this is what I see:

tests-Mac:macserver-aa test$ java -jar B4iBuildServer.jar
Build server version: 1.5
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2015-06-04 13:01:45.534:INFO::main: Logging initialized @169ms
Loading default configuration file.
AppPath=/Users/test/Desktop/macserver-aa
2015-06-04 13:01:45.652:INFO:eek:ejs.Server:main: jetty-9.1.z-SNAPSHOT
2015-06-04 13:01:45.673:WARN:eek:ejh.MimeTypes:main: java.util.MissingResourceException: Can't find bundle for base name org/eclipse/jetty/http/encoding, locale en_US
2015-06-04 13:01:45.690:INFO:eek:ejsh.ContextHandler:main: Started o.e.j.s.ServletContextHandler@71f2a7d5{/,file:/Users/test/Desktop/macserver-aa/www,AVAILABLE}
2015-06-04 13:01:45.693:INFO:eek:ejs.AbstractNCSARequestLog:main: Opened /Users/test/Desktop/macserver-aa/logs/b4j-2015_06_04.request.log
2015-06-04 13:01:45.730:INFO:eek:ejs.ServerConnector:main: Started ServerConnector@60e1ff4c{HTTP/1.1}{0.0.0.0:51041}
2015-06-04 13:01:45.973:INFO:eek:ejs.ServerConnector:main: Started ServerConnector@364a7f68{SSL-http/1.1}{0.0.0.0:51042}
2015-06-04 13:01:45.975:INFO:eek:ejs.Server:main: Started @615ms
Build server is ready
https://192.168.145.128:51042
http://192.168.145.128:51041

Then with all provisioning profiles working fine, and trying to press debug to the correct port and IP address, this is what I see:
 
Upvote 0

Simon Smith

Active Member
Licensed User
All good. Turns out NAT interfered in communication, whereas a direct IP put it on the same network. Funny though - it still communicated.
 
Upvote 0
Top