Our app just doesn't want to do an incremental update. We build the app entire week and make build for production on Monday.
However, our updating the app uses only full nupkg, not the small update nupkg.
Is it a issue that the version jumps more than one number? Here are the RELEASES:
*8B3B649704D6530ADA354FE8FCFA2E7D2 MyAPP-1.1.9627-delta.nupkg 1402520
KLK9CA610BD3AE0743CB7E8B97FB9450B MyAPP-1.1.9627-full.nupkg 96907884
HHC6604006E1ACAA31DF1454BD265EF6E MyAPP-1.1.9653-delta.nupkg 2150036
8D93FD14A152C7D95E96EF3603A214B21 MyAPP-1.1.9653-full.nupkg 96921305*
It has nothing to do with bigger version number than +1. Your RELEASES file looks fine, can you share a demo? This should work and I cant help you without demo application that I can reproduced it on.
Related
My CN1 based app has been on the App Store and Google Play for a couple of months and works fine but when I rebuild the identical code now on NetBeans locally or through CN1 Build Servers, I'm unable to scroll through the list of containers like before.
The code is similar to the CN1 contacts demo here.
From the .codenameone folder I see.....
UpdateStatus.properties
#
#Fri Mar 27 12:34:19 MDT 2020
CodenameOne_SRCzip=118
CodenameOneJar=118
CodeNameOneBuildClientJar=105
designer=108
CLDC11Jar=108
JavaSEJar=118
lastUpdate=1585334059359
guiBuilder=107
Thx #Shai for the suggestions. A few updates:
Problem still occurred with setAllowEnableLayoutOnPaint(true)
Tested the CN1 contacts list demo and scrolling worked
Primary difference with my code from that demo is that I’m using
URLImage as in the 2nd CN1 example at
https://www.codenameone.com/javadoc/com/codename1/ui/URLImage.html
I was able to get my container of rows to scroll again by removing
any use of URLImage
Tested further by adding a URLImage to certain rows and not to others
As soon as a row is assigned a URLImage it ceases to be a scrollable
contact point for the container. As long as some of the other rows
don’t have URLImages the whole container can be scrolled (when my
finger gets to one of those rows). As soon as I run a trial where
all the visible rows are URLImages, it’s not possible to scroll the
container at all.
I tried to replicate this problem with the CN1 URLImage example
ref’d above but that example links to a nestoria api that seems to
be unavailable now.
Since this still works on code compiled in Jan. but fails for that
same code recompiled now, I still wonder whether something has
changed with my build process but I’ve not been able to replicate
the issue with a CN1 demo.
Will keep this open for now in case there are further suggestions
but I can get by for now by minimizing my use of URLImage (reluctant
to call these URLImages earlier in the app session because a lot of
times the user might not even need these icons).
Thanks,
Mike
No it didn't. Try the contacts demo, it's working right? How is your code different from that.
I'm guessing you're seeing artifacts related to the optimization of setAllowEnableLayoutOnPaint(). To test this in your root form invoke:
form.setAllowEnableLayoutOnPaint(true);
Before showing it. Then see if the problem is resolved. Assuming it is try to find the area that triggers this and follow up with us based on that. Notice that setting this to true has significant scrolling performance implications.
Is there any way to make a changelog pop up when a TamperMonkey script updates?
I have already tried using LocalStorage to store current GM_info, but GM_info doesn't seem to exist/work.
I do this by hard coding a version number into my script, saving it to LocalStorage, and having the script check whether the stored version matches the version of the running script.
Rather than hard coding the version number separately, you should be able to use GM_info.script.version to access the version number from the userscript metadata block - this ought to work in both GreaseMonkey and TamperMonkey.
However, note that from version 4.0, GreaseMonkey is moving to a new API: [GM.info][1] rather than GM_info. Currently, both work in GreaseMonkey v4.1, but only GM_info works in TamperMonkey v4.4. If you've updated your script for GM4, you may have broken it for TamperMonkey.
Running WSo2 EMM 1.1.0, everything has been working just fine except for one big issue.
From the moment I first click on an app in the App Management tab, the WSO2EMM_DB.h2.db file starts to steadily grow as long as the server is running, even with absolutely no changes. Eventually, it gets so big that clicking an app on that tab takes a ridiculously long time to load the list of devices using the app. We're talking 5+ minutes, it becomes completely unusable. I have checked the error logs and found no errors at all, every time.
Restarting the server does nothing to correct the issue. Even if I click an app on the App Management tab once, and never again, the database file will continue to grow. Even restarting the server and not logging into the EMM page, it will continue to grow.
The only thing I've found so far that can possibly help is keeping backup copies of the database file and overwriting the current file when it gets too big. Obviously that's not a solution, as I'd need to create a new backup file every time there's a change on the server, and eventually the database file would grow too big from that too.
It's not an issue with the H2 database either. Not only have I tried starting over fresh several times and have had the same behavior, but here is the only info I could find regarding this issue, and they were having the issue regardless of whether or not it was on H2 or MySQL.
I've been trying to find a solution for this for over a month with no success. Any help would be appreciated!
EDIT: It looks like this might be the subject of EMM-826. Unfortunately there seems to be no response to that bug report so far.
EDIT 2: EMM-826 was closed with a message saying the following:
This issue is fixed in the EMM 1.1.0 GA latest pack. Please get all the patches for the product/build the product from the latest source [ https://github.com/wso2/product-emm ] and try again.
Unfortunately, that did not work for me. I'm not sure what exactly I'm doing wrong, so I'll list the what I did to try to fix it:
Downloaded the EMM 1.1.0 zip from http://wso2.com/products/enterprise-mobility-manager/.
Downloaded the zip from https://github.com/wso2/product-emm and pasted the files from that into my EMM_HOME directory.
When that didn't work, I searched for patches and found I was only using patches 1-6. In the documentation I found I could download patches 7-12 here. Patches 9 and 10 didn't work right for some reason; causing me not to be able to reach the EMM dashboard or publisher. I could only access the Carbon manager. I was able to make patches 7, 8, 11, and 12 work though - with no change in behavior.
Here are the steps I take to reproduce the issue:
After setting a fresh copy of the EMM up, I log in to the EMM dashboard as Admin, set up a user account, and upload an app through the Publisher.
Register a device to the user account I set up. In this case, an Android device running Android 4.2.2.
From the dashboard, I go to App Management and click the app I uploaded. The list of devices loads, but from that point on, the database file starts growing and eventually, after several hours, becomes so large it the device list will never load.
Please help!
Found this happening also, from a quick look it's the WSO2EMM_DB.notifications table. Seems to keep a history of all notifications over time, and the info for app installs is taken from non-optimized queries, which degrade as the table grows. You 'could' delete all rows from the table, and it will re-populate as devices 'check back' and report their info.
But you'd probably want to write a query to just keep the latest notification of each type of each user (I'll leave that to someone else...) and as was mentioned, it is apparently fixed in the latest version.
Issue appears to be resolved in EMM 2.0, which can be found here.
I have an issue with Click Once version number when publishing. In short, it does not start out at the current version, so I have to "publish" it repeatedly until it gets up to the right number. I am sure it is because the published version number is getting lost in the publish process, but I don't know where to look.
This is the publish process:
Dev machine modifies the app, then zips the VS project and send to the person who publishes it.
The former version files are deleted, then the new zip is unzipped, the project recompiled and published. It always starts from V1.0.0.15, and then increments one each time until we get up to the actual version.
So the question is, where is the V1.0.0.15 being stored? How to I get it to start out on the actual version number?
Greg
OK, I found it. Right click on the project, select properties, then click the publish tab. There it can be manually updated.
I am using TFS 2010.I have two team project--$project1 and $Project2
They look like-
$project1
dev
rel
$project2
main
Now I want to branch from $project1->dev to $project2, but I am getting error as "TF10169:Unsupported pending change attempted..."
Can anyone let me know is it possible to branch from one team project to another?
Branching from one Team Project to another is fully supported.
If you have a copy of Project1 mapped to your local workspace try doing a Get Latest. For completeness do a Get Specific Version and then select Latest Version to overwrite all locals rather than just Get Latest.
I've seen this error before albeit unrelated to a branch, when deletes have been pending.