There is memory leak in iOS when TextArea(maybe Label as well) setText() is called. The following codes can reproduce the issue after pressing the button for hundred times within a short period. The memory goes up after pressing the button and the memory will not be released. Please note that you have to press the button quickly for multiple times.

protected void onMain_TestLabel2Action(Component c, ActionEvent event) { int iCounter = 0; while (iCounter < 100) { TextArea testTxtArea = findRandomTextArea(c); testTxtArea.setText("Random100_" + new Date().getTime()); testTxtArea.getParent().revalidate(); iCounter++; } }

Original issue 789 created by codenameone on 2013-07-20T17:13:49.000Z:

Please clearly state whether the issue relates to a device/the simulator or the tools. This happens in real device. If related to a device be sure to specify exactly which device with as much details as possible.

On iPhone 4, latest OS version and also on Android phones.

What steps will reproduce the problem?

1. Have a device register for push using following code: Hashtable meta = new Hashtable(1); meta.put(com.codename1.push.Push.GOOGLE_PUSH_KEY, "359276012902"); Display.getInstance().registerPush(meta, false);
2. The PushCallback registeredForPush(String deviceId) is called by cn1 framework.
3. The deviceId received in the registeredForPush() for iPhone 4 device is given below:

b018aa2534e7abf5da59f9c673e255eb107cf3f771022db31d3a215c8e8f4c8b

1. after this when you try to get the cn1 specific device id, it is coming as null from the following call: com.codename1.push.Push.getDeviceKey();

What is the expected output? What do you see instead?

the cn1 specific device id which is a long value should be available so that push to specific device can be made.

What version of the product are you using? On what operating system?

Latest cn1 version on build server and latest plugin.

Please provide any additional information below.

Border now uses the implementation tiling support Default drawTile now deals with its own limits, no need to clip rect outside

PS: didn't have a use case for image border with an arrow here, please, double check this before merging. Also, please double check this with iOS just to be sure, couldn't test it here. I've also noticed it fixed the sidemenu covering the shadow.

PS2: android native tiling is fast :+1:

Original issue 1304 created by codenameone on 2015-01-23T22:53:30.000Z:

The first time you run one of my apps it has to obtain data. this is normally done over the network but can also be done with a file copied to the device. Either way if the dataset is a small one, my apps work. However larger datasets consistently crash the new VM.

In trying to narrow down the problem and create a test case I have come to the conclusion that it is not a particular operation that is causing the crash but the load.

The sample program attached will read lines from a file and run them through your CSVParser. It crashes before completion. In order to run this app you will need to set the property ios.fileSharingEnabled to true and you will need to copy the sample data file to the app on your device using iTunes.

This app runs fine on the old VM, it also runs a lot faster on the old VM, it takes about 18 seconds to complete. On the new VM it takes 38 seconds to crash without completing.

This initial data load is key to my apps and so I can't really test my apps at all on the new VM because I can't get any data to them.

I have attached the sample program, the data file you will need to run the program and the crash log I received from my iPod.

Original issue 829 created by codenameone on 2013-08-08T04:48:34.000Z:

Please clearly state whether the issue relates to a device/the simulator or the tools. Build server. If related to a device be sure to specify exactly which device with as much details as possible. Blackberry build

What steps will reproduce the problem?

1. Set the property of rim.pushBpsURL==https://cp12173.pushapi.eval.blackberry.com
2. And send RIM build 3.

What is the expected output? What do you see instead?

The build should be successful. Instead the build fails with error as in the attached file.

What version of the product are you using? On what operating system?

Latest version. On Mac. Please provide any additional information below.

Original issue 784 created by codenameone on 2013-07-16T04:32:41.000Z:

My J2ME build works on Nokia devices but failed on SE devices as it occured a message "Application error" and unable to launch the app. It used be fine on SE devices but now it doesn't work though on new created sample project.

What steps will reproduce the problem? 1.compile and send J2me build to server. 2.download the build and install to SE device 3.error message "application error" occurred after launching the app

What is the expected output? What do you see instead? The app should be run successfully as it does on emulator/Nokia devices. Unfortunately, it fails and shows the error message when attempting to run the app.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue 714 created by codenameone on 2013-05-18T23:56:00.000Z:

I have just released the second version of my iOS app. Some maintenance and a couple of new features, nothing that major.

I have one user that ran the first release without a problem. After installing second release it displays the splash screen and crashes. My app never starts. Just the one user.

She has tried deleting the old app, reinstalling, rebooting the device. Nothing helps.

She is using an original iPad running iOS 5.1.1. She sent me the crash log included below. Does this show anything relevant.

I don't know how to debug this.

Thanks

Had to attach the log as a file, too long

I have check your last commit changes and I could check that you commented the lines in the file CodenameOne_GLViewController.h

//#define INCLUDE_CONTACTS_USAGE //#define INCLUDE_CALENDARS_USAGE //#define INCLUDE_CAMERA_USAGE //#define INCLUDE_FACEID_USAGE //#define INCLUDE_LOCATION_USAGE //#define INCLUDE_MICROPHONE_USAGE //#define INCLUDE_MOTION_USAGE //#define INCLUDE_PHOTOLIBRARYADD_USAGE //#define INCLUDE_PHOTOLIBRARY_USAGE //#define INCLUDE_REMINDERS_USAGE //#define INCLUDE_SIRI_USAGE //#define INCLUDE_SPEECHRECOGNITION_USAGE //#define INCLUDE_NFCREADER_USAGE

Then I check that in the file IOSNative.m you need to instance the Location natively.

But if you commented how the location it will work properly?

I tried to read more times my code and to do some trials, but I didn't find any error in my code.

As I described here: https://stackoverflow.com/questions/52807700/intercept-an-url-with-a-given-domain-in-the-android-ios-and-javascript-ports-of

the problem is that my code works fine if the app is killed and then opened from a link, but it doesn't work if the app is opened from the icon, then it is putted in background and then it is opened again from the link: in this case, the app will show a blank white screen.

Tested on Android 7 (with this phone: https://www.gsmarena.com/huawei_honor_6x-8388.php)

Build hint: android.xintent_filter=<intent-filter><action android:name="android.intent.action.VIEW" /><category android:name="android.intent.category.DEFAULT" /><category android:name="android.intent.category.BROWSABLE" /><data android:host="example.com" android:scheme="https" /></intent-filter>

Code:

public class MyApplication {

    private Form current;
    private Resources theme;
    private String arg;

    public void init(Object context) {
        // use two network threads instead of one
        updateNetworkThreadCount(2);

        theme = UIManager.initFirstTheme("/theme");

        // Enable Toolbar on all Forms by default
        Toolbar.setGlobalToolbar(true);

        // Pro only feature
        Log.bindCrashProtection(true);

        addNetworkErrorListener(err -> {
            // prevent the event from propagating
            err.consume();
            if (err.getError() != null) {
                Log.e(err.getError());
            }
            Log.sendLogAsync();
            Dialog.show("Connection Error", "There was a networking error in the connection to " + err.getConnectionRequest().getUrl(), "OK", null);
        });
    }

    public void start() {
        if (current != null) {
            current.show();
            return;
        }
        Form hi = new Form("Hi World", BoxLayout.y());

        final SpanLabel message;
        arg = Display.getInstance().getProperty("AppArg", null);
        if (arg == null) {
            message = new SpanLabel("App launched from icon");
        } else {
            message = new SpanLabel("App launched from the url: " + arg);
        }
        hi.add(message);
        hi.show();

        hi.addShowListener(l -> {
            arg = Display.getInstance().getProperty("AppArg", null);
            if (arg == null) {
                message.setText("App launched from icon");
            } else {
                message.setText("App launched from the url: " + arg);
            }
            hi.revalidate();
        });

    }

    public void stop() {
        current = getCurrentForm();

        if (current instanceof Dialog) {
            ((Dialog) current).dispose();
            current = getCurrentForm();

        }
    }

    public void destroy() {
    }

}

Original issue 459 created by codenameone on 2012-12-31T21:45:51.000Z:

This is related to issue # 453 (http://code.google.com/p/codenameone/issues/detail?id=453). I have implemented two mechanisms necessary to support a robust Javascript interface in a minimal way. These are:

1. A shouldLoadURL event that is called whenever the browser is about to try to load a URL. It gives the developer the ability to cancel the page load, and/or handle the URL processing itself. With respect to Javascript, this allows us to design our own custom URLs that Javascript calls via window.location to send messages back into Java.
2. An executeAndReturnString() method on the BrowserComponent class that executes a javascript string and returns the string result of the processing. This method is synchronous so it makes it much more convenient to query the javascript environment and DOM from Java.

I have added support for Android, iOS, and JavaSE, and have attached the patches for these ports all separately.

I have also created a Test application to test all of this functionality (and will hopefully grow to include tests for much more CodenameOne functionality). I have added this project to the incubator: http://code.google.com/p/codenameone-incubator/source/browse/#svn%2Ftrunk%2Fshannah%2FCodenameOneTests

However I need to clean it up to make it easier for others to set it up and use it. This project includes a separate package, ca.weblite.codename1.js that is a full two-way Javascript bridge built on top of this functionality.

http://code.google.com/p/codenameone-incubator/source/browse/#svn%2Ftrunk%2Fshannah%2FCodenameOneTests%2Fsrc%2Fca%2Fweblite%2Fcodename1%2Fjs

I will be factoring this out into its own subproject and will post usage examples and more tests later today.

I have tested these changes on: iPhone 4S Android (Nexus 7) Android (HTC Magic running Android 2.1) JavaSE (the simulator)

I don't have a Blackberry test environment up and running yet, or I would have also provided a patch for it also.

The following bug can be reproduced on Android 7 only after the first capturing of a photo after that the app is just installed. To reproduce the bug again, it's necessary to remove the app and install it again (if you reinstall the app without removing it, or if you kill and restart the app, the bug cannot be reproduced). After the first taken photo, the bug disappears (until you will remove and install the app again).

This bug cannot be reproduced in the Simulator.

I report code and logs. However the same issue can be reproduced with the code published here (on Android, the first taken image after the app install is not placed in the Label): https://www.codenameone.com/blog/round-at-codemotion.html

Code:

        // Avatar default picture
        int avatarSizeMM = 10; // the avatar size in mm
        Style s = new Style();
        s.setFgColor(ColorUtil.LTGRAY);
        Label avatar = new Label(createAvatar(FontImage.createMaterial(FontImage.MATERIAL_PERSON, s, avatarSizeMM)), "Avatar");

        // Callback after taking a photo (from photocamera or file chooser)
        ActionListener callback = e -> {
            Log.p("ActionListener callback invoked");
            if (e != null && e.getSource() != null) {
                String filePath = (String) e.getSource();
                Image capturedImage = null;
                Log.p("Capured image filePath: " + filePath);
                if (filePath != null) {
                    try {
                        FileSystemStorage fs = FileSystemStorage.getInstance();
                        InputStream fis = fs.openInputStream(filePath);
                        capturedImage = Image.createImage(fis);
                    } catch (IOException ex) {
                        Log.p("IOException in loading the image: " + filePath);
                        Log.e(ex);
                    }
                    if (capturedImage != null) {
                        createAvatar(capturedImage, avatarSizeMM, avatar);
                    }
                } else {
                    Log.p("Error: \"filePath = (String) e.getSource()\" is null");
                }
            }
            Log.p("The image capture was canceled by the user (e.getSource() is null)");
        };

        // Button to take a photo from photocamera
        Button camera = new Button("Fotocamera", FontImage.createMaterial(FontImage.MATERIAL_CAMERA, "Avatar", 5));
        camera.addActionListener((e) -> {
            Log.p("The native photocamera is going to be opened");
            Capture.capturePhoto(callback);
        });

After the first taken photo, the callback is not invoked. The log is only: [EDT] 0:0:39,881 - The native photocamera is going to be opened

After the second taken photo, the log is (note that the last line of log doesn't make sense, I didn't cancelled the image capture) :

[EDT] 0:0:39,881 - The native photocamera is going to be opened
[EDT] 0:7:54,190 - The native photocamera is going to be opened
[EDT] 0:7:59,700 - ActionListener callback invoked
[EDT] 0:7:59,700 - Capured image filePath: /storage/emulated/0/Pictures/Registrazione/IMG_20180509_204014.jpg
[EDT] 0:8:0,45 - The image capture was cancelled by the user (e.getSource() is null)

After the third taken photo, the log is:

[EDT] 0:0:39,881 - The native photocamera is going to be opened
[EDT] 0:7:54,190 - The native photocamera is going to be opened
[EDT] 0:7:59,700 - ActionListener callback invoked
[EDT] 0:7:59,700 - Capured image filePath: /storage/emulated/0/Pictures/Registrazione/IMG_20180509_204014.jpg
[EDT] 0:8:0,45 - The image capture was canceled by the user (e.getSource() is null)
[EDT] 0:15:2,647 - The native photocamera is going to be opened
[EDT] 0:15:13,567 - ActionListener callback invoked
[EDT] 0:15:13,568 - Capured image filePath: /storage/emulated/0/Pictures/Registrazione/IMG_20180509_204723.jpg
[EDT] 0:15:13,840 - The image capture was canceled by the user (e.getSource() is null)

Text field edit dialog, when the keyboard on the iPhone is triggered for typing has the following flaws: [1] – The editing area is positioned at the top of the interface where we have the interference of the front camera area, making it difficult to read and / or type the 1st line.
See illustrative images bellow:

[2] – As we edit and fill in the editing area: when we reach the bottom of the editing area, does not occur the expected vertical scroll, it is not possible to vertically scroll the text and as we continue to edit the new inserted words is below the visible area (covered by the keyboard area). See illustrative images bellow:

We generated an APP project using cn1 and ran the same on XCODE on a MacBook Pro: In XCODE the following message was displayed:

2023-01-07 09:13:46.607428-0300 IwCareAppPro[92509:4612587] [LayoutConstraints] Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) ( "<NSAutoresizingMaskLayoutConstraint:0x60000837a530 h=--& v=--& _UIToolbarContentView:0x7f8df8f69910.width == 0 (active)>", "<NSLayoutConstraint:0x600008375540 H:|-(0)-[_UIButtonBarStackView:0x7f8df8f73e80] (active, names: '|':_UIToolbarContentView:0x7f8df8f69910 )>", "<NSLayoutConstraint:0x600008375590 H:[_UIButtonBarStackView:0x7f8df8f73e80]-(0)-| (active, names: '|':_UIToolbarContentView:0x7f8df8f69910 )>", "<NSLayoutConstraint:0x60000832b070 'TB_Leading_Leading' H:|-(20)-[_UIModernBarButton:0x7f8dfa1da3a0'Done'] (active, names: '|':_UIButtonBarButton:0x7f8dfa1da170 )>", "<NSLayoutConstraint:0x60000832b0c0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x7f8dfa1da3a0'Done']-(20)-| (active, names: '|':_UIButtonBarButton:0x7f8dfa1da170 )>", "<NSLayoutConstraint:0x60000837a080 'UISV-canvas-connection' UILayoutGuide:0x60000195c700'UIViewLayoutMarginsGuide'.leading == UIView:0x7f8dfa1d9fc0.leading (active)>", "<NSLayoutConstraint:0x60000837a0d0 'UISV-canvas-connection' UILayoutGuide:0x60000195c700'UIViewLayoutMarginsGuide'.trailing == _UIButtonBarButton:0x7f8dfa1da170.trailing (active)>", "<NSLayoutConstraint:0x600008379ae0 'UISV-spacing' H:[UIView:0x7f8dfa1d9fc0]-(0)-[_UIButtonBarButton:0x7f8dfa1da170] (active)>", "<NSLayoutConstraint:0x600008375450 'UIView-leftMargin-guide-constraint' H:|-(0)-UILayoutGuide:0x60000195c700'UIViewLayoutMarginsGuide' (active, names: '|':_UIButtonBarStackView:0x7f8df8f73e80 )>", "<NSLayoutConstraint:0x6000083754f0 'UIView-rightMargin-guide-constraint' H:[UILayoutGuide:0x60000195c700'UIViewLayoutMarginsGuide']-(0)-|(LTR) (active, names: '|':_UIButtonBarStackView:0x7f8df8f73e80 )>" )

Will attempt to recover by breaking constraint <NSLayoutConstraint:0x60000832b0c0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x7f8dfa1da3a0'Done']-(20)-| (active, names: '|':_UIButtonBarButton:0x7f8dfa1da170 )>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful. 2023-01-07 09:14:11.184859-0300 IwCareAppPro[92509:4612587] [com.apple.VisionKit.processing] Analysis not completed because device does not support Image Analysis. This will only be logged once. 2023-01-07 09:14:11.207965-0300 IwCareAppPro[92509:4612587] [com.apple.VisionKit.RemoveBackground] Request to remove background on an unsupported device. Error Domain=com.apple.VisionKit.RemoveBackground Code=-8 "(null)" 2023-01-07 09:14:11.208509-0300 IwCareAppPro[92509:4612587] [UILog] Called -[UIContextMenuInteraction updateVisibleMenuWithBlock:] while no context menu is visible. This won't do anything. 2023-01-07 09:14:11.628923-0300 IwCareAppPro[92509:4612985] LaunchRichTextEditor : iwvar_quadroclinico

We configure the simbolic breakpoint as suggested by XCODE, below the image of what is was displayed:

I really want to start to translate the wiki to Portuguese (Brazil), but, I didn't found a correct way to make the same wiki have multiple languages. So I want some opinions of how anybody that wants to translate wiki of CodenameOne can achieve that.

Describe the bug this is the output at the end of the log:

[INFO] Process return code is 0
[INFO] Executing: 
[INFO] javac -source 1.6 -target 1.6 -classpath *_omitted the paths here_*
[INFO] Executing with timeout -1
[INFO] Warning: [options] Bootstrap Classpath not specified with -source 6
[INFO] Error: Source option 6 is no longer supported. Use 7 or higher.
[INFO] Error: Target option 6 is no longer supported. Use 7 or higher.
[INFO] Process return code is 2

But I couldn't figure it out where 1.6 is set anywhere in the poms. This (with 1.8)is written in the root pom for example:

  <properties>
    <java.version>1.8</java.version>
    <cn1app.name>app</cn1app.name>
    <maven-compiler-plugin.version>3.8.0</maven-compiler-plugin.version>
    <rhino.version>1.7.11</rhino.version>
    <cn1.plugin.version>7.0.95</cn1.plugin.version>
    <maven.compiler.target>1.8</maven.compiler.target>
    <java-tests.version>11</java-tests.version>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <cn1.version>7.0.95</cn1.version>
    <maven.compiler.source>1.8</maven.compiler.source>
  </properties>

To Reproduce just running "Xcode iOS Project" config via IntelliJ

Expected behavior Generating a fresh xcode project

Additional context I'm not sure if this is a bug, because the config is not that fresh (Beginning of 2022), but why is javac called with 1.6 when maven.compiler.target and maven.compiler.source are set to 1.8?

Describe the bug CN1 seems to use deprecated Android API which isn't supported on Android 12 anymore

To Reproduce Steps to reproduce the behavior: Just check the specific line of the AndroidLocationManager mentioned in the stacktrace

Expected behavior No crash

Smartphone (please complete the following information):

• Device: Emulator
• OS: Android 12

Additional context

2022-12-25 14:56:16.217 2188-2188/org.igmg.android E/AndroidRuntime: FATAL EXCEPTION: main
    Process: org.igmg.android, PID: 2188
    java.lang.UnsupportedOperationException: GpsStatus APIs not supported, please use GnssStatus APIs instead
        at android.location.LocationManager.addGpsStatusListener(LocationManager.java:2344)
        at com.codename1.location.AndroidLocationManager$2.run(AndroidLocationManager.java:150)
        at android.os.Handler.handleCallback(Handler.java:938)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loopOnce(Looper.java:201)
        at android.os.Looper.loop(Looper.java:288)
        at android.app.ActivityThread.main(ActivityThread.java:7839)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)

The App works quite well after login , but it becomes increaesily slow after some activities and finaly crashes. The issue occur´s only in iOs version (on Android works well).

This behavior became more critical after upggrading iOS to 16.1 version. Running on iOs 15 this issue was not so critical.

It seems like a memory retrieving issue. Is there any codenameone orientation about this ?