Search Results

In debug mode, the debugger adds a request to keep the process running for a few more minutes. You can also do it with this code: https://www.b4x.-of-services-in-ios.130536/post-821810 However this is not the correct solution for background playback. You need something like: https://www.b4x.-playb
link: So I already have a configureAudioSession Objective C code added, that is what allows the video to play in PIP mode, and I can see the small window st
link: Hi All, I recently shared this project that allows you to play a video in PIP (Picture in Picture) Mode, what I didn't realize is that it only works w
link: Not sure if this will help, but I have checked everything in my project and I can't see what can be different between running in debug mode and releas

iReleaseLogger combined with the desktop B4iLogger tool (written with B4J) allow you to monitor the app logs in release mode. This is useful when you encounter an error that you are unable to reproduce in debug mode. The release logger sends udp messages which the desktop logger prints. Depending o
link: The current tool is indeed intended for local usage, though it can be extended in the future to support the use case which you describe.
link: Thanks for this, but since no more TestFlight, this can work only on my local phone if some tester has different phone with issue, how can I send him

If you can run your app in debug mode then you can also run it in release mode.
link: Thank you Erel. Once I complete the account creation process, I will also test in release mode.

Release mode is available under Tools - Build Server - Build Release App, however it will be slower than debug compilation. This error might be related to the process timeout. What do you see in the IDE when it happens?
link: Is b4i have another mode? I have only debug mode. Could you check the log? I think compiling has an error and is stuck. IDE is not showing it. ja

You are using an old device that is 32 bit. In release mode it creates binaries for both types of CPUs. It means that B4i-Bridge will run the app after installation. Keep it checked. In the past it was faster to start the app yourself.
link: they are OK (I think), I use them to install the App in release mode. that is correct? : 90570
link: The correct solution is to get debug working. If it works in release mode and doesn't work in debug mode then the first thing to check is the CPU sett

In my opinion, this is the easiest way ...... The way I do it is get the customer's UDID. Ask them to get it from "get.udid.io" and send it to you. Add the UDID to the provisioning profile. Use B4I to build the (ad-hoc) release app. Upload the release app using OTA Deployer. Send the link from OTA

No. It moves to the background. It might be killed at some point. You can handle the B4XPage_Background event to log the user out. I'm not sure that logging the user out immediately is the best idea.
link: I just compiled and installed my iOS app for the first time in release mode - all went well and the app runs fine. But, my app's first page is the log

Go to menu: Tools -> Build server -> Build Release App
link: After upgrading to v4.80 it seems that only debug mode compilation is possible. No release mode compilation is offered.
link: Thanks for the help

This is not really an error. It is completely fine to compile in release mode with non-store provision profile. It is only when you want to make a store build that you should use a store PP.

In release mode it works . Debug mode , it takes more than a minute . Any workaround ?

Powered by ColBERT