Package creation overwrites version number while submitting to WP store

I'm creating a package for submission the first time and I have set the version to 1.1.0.0, but when the package is uploaded to the associated app in Dev center, the package version is showing as "2015.203.1452.4045" instead of "1.1.0.0".
I really do not want the app to be published with a major version of 2015. I went and did a search on the entire solution for the version, but couldn't find any reference.
package.appxmanifest shows
<Identity Name="AppID" Publisher="PubID" Version="1.1.0.0" />
What am I doing wrong?

Bumping.
I still haven't figured anything out in this respect.  Assistance would be greatly appreciated.

Similar Messages

  • Creation of Auto Number while creating Masters

    Hi Experts
    Please let me know the process of creating Auto Generated Numbers while creating Masters.
    I have requirement of creating Masters for -
    1. Customers
    2. Items
    (Where Auto Generated Numbers are required).
    Regards

    Hi Prashant,
    If you want auto generated number then as sugeested in the above post you have to go for Key Generation.
    In Console where you define remote system ,there you have to make keygeneration Yes and specify the start and end limit in from and to.
    Now whenever a record is created and syndicated to this particular remotye system for which key generation is set ,system will assign a autogenerated number.
    Without syndication number will not be generated.
    And if you want to maintain different number ranges for different lookup values then go for qualified number range.
    Or  if you simple want auto generated number starting from 1 to maintain count of records in MDM then maintain a field with type autoid.
    Regards,
    Neethu Joy

  • Wants to change BPEL Process Version Number while compiling

    When I build the process via Jdeveloper, It creates the jar file with the name of *BPELProcess11 v201109_17__42581.jar* .But my requirement is each and everytime I compile the process Its name should be like this BPELProcess11_v1.jar. I have changed the build.properties file but still unable to find the solution even change the *.jar file.
    Thanks

    Hi',
    I doubt if this is possible, Still Gurus can confirm this.
    Right click on your project > Project Properties > Deployment
    Deployment Profiles > <project-name>(SOA-SAR File) > click EDIT > General.
    This is where your .jar file name gets created, I doubt if this can be modified, or if there is a way to edit this.
    -Yatan

  • How to pass version number of process using API's

    Locator locator = new Locator("default","bpel");
         IDeliveryService deliveryService = (IDeliveryService) locator.lookupService(IDeliveryService.SERVICE_NAME );
         // Construct a normalized message and send to Oracle BPEL Process Manager
    NormalizedMessage nm = new NormalizedMessage();
    nm.addPart("payload", xml);
    // Initiate the BPEL process
    deliveryService.post("AsyncProc1", "initiate", nm);
    When I run this code, I get the following error:
    09/03/31 15:07:46.953 workflowform: Servlet error
    ORABPEL-02178
    Process not found.
    The BPEL process "AsyncProc1", revision "" has not been loaded. Either the process was not initialized properly or the process has
    been disabled.
    Please consult your administrator regarding this error. The application server logs may provide more information regarding this error
    I had created many versions of the same process. I need to use version 4.0 of this workflow. Is it possible to pass the version number while initiating the process?
    Thanks.

    Hi Badri,
    I think you can identify the bpel with different versions as follows:
    bpelprocessName_1.1 or bpelprocessName_v1.1
    either one of these should be correct.
    Thanks
    Saikrishna

  • Display Package version number in HTML?

    Hi,
    My customer wants to display the version number of the apps/xx package in the HTML.
    I'm just wondering if this is a good idea, i.e. the actual package contents could be overwritten, but the package doesn't change.
    Also - how could that be achieved?  There is a services JSP in the CRX package manager - could that be used?
    http://localhost:4502/crx/packmgr/service.jsp
    Thanks!

    The subject line & description looks contridactory. I am assuming you are looking for package version, For that You should be able to get using jcr package api [1]. Ex:- vJcrPackageDefinition.getId().getVersionString()
    http://dev.day.com/docs/en/cq/current/javadoc/com/day/jcr/vault/packaging/JcrPackageDefini tion.html

  • Error - The version number in the package is not valid. The version number cannot be greater than current version number

    whats does this error mean
    i download 2008 r2 and try to open package but still getting error
    Error 1
    Error loading  The version number in the package is not valid. The version number cannot be greater than current version number.  
    Error 2
    Error loading Package migration from version 8 to version 3 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.".  

    can you tell me which version it is >
    i try to fix in dtexec
    getting following error :
    Started:  2:02:13 PM
    Error: 2015-01-30 14:02:14.68
       Code: 0xC000F427
       Source: Member Eligibility
       Description: To run a SSIS package outside of SQL Server Data Tools you must
    install Member Eligibility of Integration Services or higher.
    End Error
    Warning: 2015-01-30 14:02:14.69
       Code: 0x80019002
     Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution
     method succeeded, but the number of errors raised (2) reached the maximum allow
    ed (1); resulting in failure. This occurs when the number of errors reaches the
    number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the e
    rrors.
    End Warning
    DTExec: The package execution returned DTSER_FAILURE (1).
    Started:  2:02:13 PM
    Finished: 2:02:14 PM
    i cannot upgrade original package

  • Question nVidia Chipset Drive Package Version Number.

    Question nVidia Chipset Drive Package Version Number.
    Hope this question is in the right sub forum.
    I have see this question asked on several Forums, but never see a answer.
    How do you tell which Chipset Driver Package Version is installed on your system, other than going to the Device Manager calling up the properties for each device and record the version number and comparing it to what listed for the Drive Package version?
    Roger

    I agree with you Richard.
    I wouldn't say super fast ram though, I buy Crucial. It is very nice ram and does not break the bank. (no heatsinks on it or any other expenses)
    Maybe I offended you, Bcc, by accident. I'm just trying to help folks on these forums and I have been with the nforce since day one. I have never seen this issue happen (or anything like it) on this board.
    Like my suggestion, (if that didn't work, I would have continued to work) if I couldn't disable the agp host I would have uninstalled it (the device itself) and let windows try again. It could have been an nforce package issue and not with the detonator. I wish when these problems occurred, that I had the opportunity to try and fix these very rare occurences and examine the issue at my own desk.
    I see too many people jump to the conclusion that they have found the mystery bug and go tell nvidia to recall the boards and fix it. I would not try to tell you that you are clueless about computers, as I don't have any idea how well you know them. But as an experienced technical writer/helper, I'm inclined to speak to the people as if they are dumb. As you can guess, many aren't, and they think that I may be saying they are, but at least they understand the situation.
    More than the majority of problems are caused by heat. Too much heat will cause funny things to start happening to your computer. Sometimes it's just the ram, or maybe the cpu that get overheated. With summer coming, it's prime time to see the 'heat' problem creep up. I'm sure this wasn't the case with your issue, but it is overlooked most of the time.
    Anyway, I'm glad your happy and your problem is fixed.

  • MANUAL CREATION OF BATCH NUMBER(EXTERNALLY)    -   NOT TO BE ALLOWED

    MANUAL CREATION OF BATCH NUMBER(EXTERNALLY)   -  NOT TO BE ALLOWED while creation of Process Orders.

    Hi,
    Check t code OMCZ whether internal Batch no assignment is active or not.
    From F1 help
    In this step:
    you activate internal batch number assignment
    you define whether internal batch number assignment is allowed for goods receipts that have an account assignment
    Standard settings
    The standard version of the SAP system contains a predefined number range.
    Further notes
    Batch number assignment uses two function model exits with which you can define templates for batch numbers. You make the necessary settings in work step function module exits for internal batch number assignment.
    The system checks whether the assigned batch number already exists in the system. Should the number already exist, the function is terminated.
    When creating a client by copying another client, please note that internal number assignment is not active in the target client. You must activate it manually.
    Regards
    Anupam Sharma

  • Unable to use the Copy function while submitting the program for XML output

    Hi
    when i submit the concurrent program with XML output type, getting the output..
    when i submit he concurrent program using the copy button not able to get the output,
    my observation
    while submitting the program the xml template is not called....
    Diagnostics--> view xml -- able to view the ouput.
    do let me know if any of the steps is missing while registration in the xml responsibility..
    this is only with the custom conc program.. the standard program is working fine...
    do help me out..
    Regards
    Yram

    It's really a little difficult to answer your question without a bit more information. What version of JDeveloper are you using? What's your technology stack?
    If this is JDeveloper 11+g+, with the Fusion technology stack, you can use a technique like the one described here:
    http://groundside.com/blog/GrantRonald.php?title=jdeveloper_11_business_services_cascadin&more=1&c=1&tb=1&pb=1
    If it's JDeveloper 10.1.3, with the default Web technology stack, look here:
    http://radio.weblogs.com/0118231/stories/2004/09/23/notYetDocumentedAdfSampleApplications.html#62
    If, as it looks like, this is really a question about generic JSPs (no JSF), you might actually have a bit more success on a generic JSP forum--using scriptlets hasn't really been best practices within JDev since...well, since JSTL became available, really. That was a number of years ago.
    Like I said, there's really no direct way to use Javascript output in a scriptlet--unless you mean something like storing Javascript output in a hidden field, and using the value in a scriptlet on the next request. But by the time Javascript runs, any scriptlet from the current request will already have executed.

  • How to Run 2012 SSIS packages on 2008R2 Version

    HI Friends,
    I have scheduled a job to run 2012 SSIs packages on 2008R2. I am getting this error can you please Give any ideas how can I run them without converting!
    ERROR Is :
    Package migration from version 6 to version 3 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number."

    Hello,
    There is backward compatibility in SSIS but no forward compatibility, meaning, when 2008 R2 is developed they were aware of all versions less than 2008 R2 and included execution scenarios , this is backward compatibility
    while 2008 R2 is being developed , 2012 is not yet developed. so we cannot execute a 2012 package on 2008 R2 Server where vice versa is possible 
    Correct.
    The "backwards compatibility" is implemented by SSIS upgrading older versions of packages to the current version of SSIS when executing. If the upgrade fails, you're out of luck.
    MCSE SQL Server 2012 - Please mark posts as answered where appropriate.

  • The version number cannot be greater than current version number

    i am deployingmy ssis package which is in 2012.(version 6)
    and my ssis server also in 2012.
    but i am getting error:
    "the version number in package is not valid, the version number cannot be greater than current verison number"
    and one more thing how to see ifmy package is in 2012,by looking it in notepad?

    Hi coool_sweet,
    Based on the error message that "The version number in the package is not valid. The version number cannot be greater than current version number.", we can infer that the underlying cause may be that the current SSIS package is created in SQL Server
    2012, while you are trying to open or execute it in SQL Server 2008R2 or earlier versions.
    As to your scenario, I guess you are using old version of the DTEXEC instead of the new one to run the package. That means, the exe shipped with 2008R2 or earlier versions is picked up when it is expected to use the one shipped with 2012. So, obviously this
    happens when SQL Server 2012 is running along with SQL Serve r2008R2 or earlier versions on the same machine.
    To fix this issue, there are three workarounds to correct this.
    Hard code the path of SQL Server 2012's DTEXEC while calling the SSIS package as shown below.
    C:\Program Files\Microsoft SQL Server\110\DTS\Binn\DTEXEC.exe /F "D:\MyFolder\MyPackage.dtsx"
    Rename the old exe in the 2008R2 path to a different name (Example:- C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTEXEC_Old.exe)
    Go to PATH environmental variable and edit it in such a way that "C:\Program Files\Microsoft SQL Server\110\DTS\Binn" path appears well before the "C:\Program Files\Microsoft SQL Server\100\DTS\Binn" path.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • AppManifest.xml is being generated with the wrong version number

    I am having a interesting problem which is preventing me from submitting an update to my app to the Windows Phone Store. I have done this 100 times and something is wrong with visual studio building the .xap file. Steps I am taking:
    Update all version references in project settings and appmanifestWM to 1.4.0.0
    Build Release version
    Copy .xap from /bin/release
    Upload as an app update to windows phone dev site
    What happens is that the current version of the app (1.3.1.0) is still listed as the version of the app that the submission page is parsing out of the version (1.4.0.0) .xap file. I unzipped the xap file and looked at the appmanifest files and found that
    the AppManifest.xaml has the correct version number but the AppManifest.xml still has version 1.3.1.0. If anyone could help me resolve this issue it would be greatly appreciated.

    Thanks for your reply. I believe it is a bug with my solution because I have now tried all of these steps on two computers and uploaded using two different browsers and I still get a AppManifest.xml file that has version 1.3.1.0. I will copy and paste the
    unzipped code from the AppManifest.xml file.
    <?xml version="1.0" encoding="utf-8"?>
    <Package xmlns="http://schemas.microsoft.com/appx/2010/manifest" xmlns:m2="http://schemas.microsoft.com/appx/2013/manifest" xmlns:m3="http://schemas.microsoft.com/appx/2014/manifest" xmlns:mp="http://schemas.microsoft.com/appx/2014/phone/manifest" xmlns:build="http://schemas.microsoft.com/developer/appx/2012/build" IgnorableNamespaces="build">
    <!--
    THIS PACKAGE MANIFEST FILE IS GENERATED BY THE BUILD PROCESS.
    Changes to this file will be lost when it is regenerated. To correct errors in this file, edit the source .appxmanifest file.
    For more information on package manifest files, see http://go.microsoft.com/fwlink/?LinkID=241727
    -->
    <Identity Name="50523CameronStair.MyDebts" Publisher="CN=FA4BA529-B82F-4A0F-A35C-6700BC51B3E1" Version="1.3.1.0" ProcessorArchitecture="neutral" />
    <mp:PhoneIdentity PhoneProductId="c805a27c-951f-4c0d-a831-1126f9a70563" PhonePublisherId="51beaec0-db37-4002-81de-5e138a756b34" />
    <Properties>
    <DisplayName>MyDebtsApp</DisplayName>
    <PublisherDisplayName>Cameron Stair</PublisherDisplayName>
    <Logo>Assets\StoreLogo.png</Logo>
    </Properties>
    <Prerequisites>
    <OSMinVersion>6.3.1</OSMinVersion>
    <OSMaxVersionTested>6.3.1</OSMaxVersionTested>
    </Prerequisites>
    <Resources>
    <Resource Language="EN-US" />
    </Resources>
    <Applications>
    <Application Id="App" Executable="AGHost.exe" EntryPoint="MainPage.xaml">
    <m3:VisualElements DisplayName="My Debts" Square150x150Logo="Assets\SquareTile150x150.png" Square44x44Logo="Assets\Logo.png" Description="A debt tracker app." ForegroundText="light" BackgroundColor="#464646" ToastCapable="false">
    <m3:DefaultTile Square71x71Logo="Assets\SquareTile71x71.png"></m3:DefaultTile>
    <m3:SplashScreen Image="Assets\SplashScreen.png" />
    </m3:VisualElements>
    <Extensions>
    <Extension Category="windows.backgroundTasks" EntryPoint="AgHost.BackgroundTask">
    <BackgroundTasks>
    <Task Type="systemEvent" />
    </BackgroundTasks>
    </Extension>
    </Extensions>
    </Application>
    </Applications>
    <Extensions>
    <Extension Category="windows.activatableClass.inProcessServer">
    <InProcessServer>
    <Path>AgHostSvcs.dll</Path>
    <ActivatableClass ActivatableClassId="AgHost.BackgroundTask" ThreadingModel="both" />
    </InProcessServer>
    </Extension>
    </Extensions>
    <Capabilities>
    <m3:Capability Name="contacts" />
    </Capabilities>
    <build:Metadata>
    <build:Item Name="TargetFrameworkMoniker" Value="WindowsPhone,Version=v8.1" />
    <build:Item Name="VisualStudio" Version="12.0" />
    <build:Item Name="VisualStudioEdition" Value="Microsoft Visual Studio Professional 2013" />
    <build:Item Name="OperatingSystem" Version="6.3.9600.16384 (winblue_rtm.130821-1623)" />
    <build:Item Name="Microsoft.Build.AppxPackage.dll" Version="12.0.31101.0" />
    <build:Item Name="ProjectGUID" Value="{C805A27C-951F-4C0D-A831-1126F9A70563}" />
    <build:Item Name="MSAdvertising" Version="6.1" />
    <build:Item Name="MakePri.exe" Version="6.3.9600.17298 (winblue.141024-1500)" />
    </build:Metadata>
    </Package>
    As you can see the package version being generated is wrong. Can you explain where exactly in the solution that value is taken from? I thought it was from WMAppManifest but I could be wrong. 
    Edit: In looking at the code above and then rereading what I wrote I realized my blaring error. I completely forgot that Silverlight 8.1 apps have an appxmanifest as well and that data is drawn from that as well as WMAppManifest. I never updated the version
    in that appxmanifest. Thank you for the help and I apologize for my stupidity.

  • Version number conflicts with NI custom data types

    Custom data type version number conflicts
    Options
    Mark as New
    Bookmark
    Subscribe
    Subscribe to RSS Feed
    Highlight
    Print
    Email to a Friend
    Report to a Moderator
    07-11-2011 08:10 AM
    I am new to Teststand software interface.  While doing my first software release under the guidance of a more experienced colleague, we discovered that Teststand will not run if it detects version number conflicts between custom data types on my machine vs. the production test machine.  I verified differences between all .seq files in my test program directory, but I did not realize that the version number difference exists in the StationGlobals.ini file, which is stored in a different location.  After discovering this, I modified the version number in one of the files.  However, two releases later, I discovered that the version number mismatches in another two files.  This raises several questions for me :
    1.  Is there a way in Teststand to view all the .seq files where a custom data type is used and then change its version number in one attempt?
    2.  Under what instances does Teststand upgrade the version number of a custom data type?
    3.  Are there any tools or scripts within Teststand that can allow the version number of custom data types to be changed in all .ini files when a difference is discovered between the current production test station settings and a new release?
    Please help.

    Have you read this?  http://zone.ni.com/devzone/cda/tut/p/id/7060
    I can tell you that your situation is not uncommon with TestStand.  The key is just doing it right the first time.  haha
    #1- I doubt that this is possible because then TestStand would have to know every location of every .seq on the machine.  You will only see it when you open the sequence file.
    #2- TestStand updates the version every time you change it.  You should get a message popup when you try to save that asks if you want to increment the version or not.  There's also a check box that says Remove Modified Mark From Types.  Look under Station Options in the File tab.  There are some settings there about Type conflicts.
    #3- http://zone.ni.com/devzone/cda/tut/p/id/7910
    http://digital.ni.com/public.nsf/allkb/4153576DA04BEB098625743D00704A09
    Hope this helps,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • How Do I Find Out a Folio Version Number

    Hi Guys,
    So far, everytime I have submitted a folio to the App Store, I have received a variation of the following error:
    Version Mismatch - Neither CFBundleVersion ['3.4.2.9.91210'] nor CFBundleShortVersionString ['1.0.8'] in the Info.plist match the version of the app set in iTunes Connect ['2.0'].
    I'd like to be able to put the correct version number into iTunes Connect when I upload the App, but how do I find it? Where is the CFBundleShortVersionString for each folio located?
    Cheers
    Chris

    It isn't necessary to change that number—Apple is just giving you a housekeeping warning—but if you really want to edit the version number in iTunes, you can find it in DPS App Builder.

  • How do I make my iPhoto Library's version number appear in the Get Info window?

    I recently (within the past 2 weeks) purchased a new 27 inch iMac and have been importing data (applications and files) from my 2010 Macbook Pro via AirDrop.  One of the first files I migrated over was my iPhoto Library.  I doing so, I noticed a few differences between its file attributes and those of the iPhoto Library file created by default on my new computer - two of which I'll note here.  First, I noticed that the file resident on my new OS was labeled iPhoto Library.photolibrary while my older version did not have the ".photolibrary" extension.  That seemed simple enough to correct so I added that extension to my old library file.  The second difference I'd note - and the source of my question - is that the default iPhoto Library file displayed a version number (9.5.1) in its "Get Info" window, while mine did not.  I checked my file's info.plist file and the correct information seems to be listed.  It reads (in part):
    <dict>
                   <key>CFBundleGetInfoString</key>
                   <string>iPhoto Libary 9.5.1</string>
                   <key>CFBundleShortVersionString</key>
                   <string>9.5.1</string>
    </dict>
    </plist>
    I'm not sure this is really a question for the iPhoto community, as it seems like a more general issue; but, this is my first post to these forums, and I didn't know where to start.  Thanks in advance for the advise/suggestions.

    In terms of the info.plist file, I only reviewed it to see why I wasn't seeing the version number in the GetInfo window.
    The string "<key>CFBundleGetInfoString</key>
                   <string>iPhoto Libary 9.5.1</string>"
    is exactly what will be shown in the Get Info panel. I tested that by simply editing this string in a test library using XCode. I could "Get Info" to show ridiculous versions numbers this way.
    However, none of my older iPhoto libraries will show the version string in Get Info, only libraries I created with iPhoto 9.5.1. or Aperture 3.3 or later.
    There is probably one of the other database files in the folder "database" - *.appdb and *.db  interfering.  None of the Library First Aid options did make the version number show for my older iPhoto libraries - not even rebuilding the iPhoto library. The only way I could make the version number show in "Get Info" was by exporting the library as a new library using Aperture. But this exported library is now showing as Aperture library.

Maybe you are looking for