Android application manager shows wrong app name - package

Does anyone know why the application manager, found by going to settings->application manager, is showing the wrong name for my application? I installed my app twice under different names and with different application package names. I can see both named applications under the apps page, but the application manager is showing them as the same name. I need to know which is which so I can force close and uninstall the correct version of my application. Any ideas?
Here's the manifest of the DEMO version of my application, where string/app_name = package_DEMO:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="my.apps.package_DEMO"
android:versionCode="1"
android:versionName="0.0">
<uses-sdk
android:minSdkVersion="10"
android:targetSdkVersion="10"/>
<application android:label="#string/app_name"
android:name="my.apps.package.MyApplication"
android:icon="#drawable/ic_launcher"
android:theme="#style/AppTheme"
android:launchMode="singleTask"
android:debuggable="true">
<activity android:label="#string/app_name"
android:configChanges="orientation|keyboardHidden"
android:name="my.apps.package.MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:label="#string/app_name"
android:configChanges="orientation|keyboardHidden"
android:name="my.apps.package.SettingsActivity">
</activity>
</application>
</manifest>
And the original's manifest, where string/app_name = package:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="my.apps.package"
android:versionCode="1"
android:versionName="0.0">
<uses-sdk
android:minSdkVersion="10"
android:targetSdkVersion="10"/>
<application android:label="#string/app_name"
android:name="my.apps.package.MyApplication"
android:icon="#drawable/ic_launcher"
android:theme="#style/AppTheme"
android:launchMode="singleTask"
android:debuggable="true">
<activity android:label="#string/app_name"
android:configChanges="orientation|keyboardHidden"
android:name="my.apps.package.MainActivity">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:label="#string/app_name"
android:configChanges="orientation|keyboardHidden"
android:name="my.apps.package.SettingsActivity">
</activity>
</application>
</manifest>

I had this problem - i.e. that of the app name showing up incorrectly in Settings->Apps
I managed to fix it by rebooting the device.
My guess is that the android application manager was caching the 'old' name until a reboot. I confirmed this by changing the app name and redeploying - the old name shows in settings->aps until a reboot.

It is probably because of your manifest file. If you copied your code and only refactored the package names, eclipse does not change the name of your application in the manifest file.
Either change directly, or use your string.xml files
android:label="#string/app_name"

you can add android:label="YOUR NAME APP"
<application
android:label="YOUR NAME APP"
android:allowBackup="true"
android:icon="#drawable/logo">

You can uninstall the package name by connecting your phone to the pc...
Go to the command prompt
adb uninstall packagename
so if you want to delete an an app with package name com.example.test
Type : adb uninstall com.example.test in command prompt...
Note :
adb should in the system path
or else run this command from your sdkfolder/platform-tools/

I just uninstalled, cleaned, and reinstalled for like the 50th time, and magically the app names are different under the application manager. This must be a system bug, because both versions of the app were showing different names in the activity labels, and under the "apps" page on the device eariler. I'll try seeing if I can reproduce it again.

Related

BVN404 gadget showing in local dev, but not EpiServer integration enviornment

I am able to access this gadget in my local dev environment, but not integration, as you can see below:
Local dev:
Integration:
I double checked the BVN settings from here: https://github.com/Geta/404handler#configuration. They are setup like this in my web.config:
<section name="bvn404Handler" type="BVNetwork.NotFound.Configuration.Bvn404HandlerConfiguration, BVNetwork.EPi404" />
<episerver.shell>
<publicModules rootPath="~/modules/" autoDiscovery="Modules" />
<protectedModules rootPath="~/EPiServer/">
<add name="BVNetwork.404Handler" />
<bvn404Handler handlerMode="On">
<providers>
<add name="Custom Handler" type="CompanyName.Business.CustomPageNotFoundHandler, companyname-cms" />
</providers>
</bvn404Handler>
There is not a securedComponents section, though I did try to add one with allowedRoles="Administrator", allowedRoles="*", and allowedRoles="Everyone" for testing purposes.
Any ideas why the gadget can't be viewed when published?
The issue was that the BVN zip file did not publish to the modules folder for some reason. After adding it back, it worked as expected.
Nuget installations sometimes misses the protectedmodules section
Ensure the BVNetwork.404Handler is in your protectedModules collection in web.config. Nuget sometimes miss that.
<episerver.shell>
<protectedModules rootPath="~/EPiServer/"> <!-- this line may vary -->
<!-- other modules -->
<add name="BVNetwork.404Handler" />
</protectedModules>
</episerver.shell>

click on link ask permission for app / browser using Ionic deeplinking dynamically

Guys don't mark this question as duplicate, as i gone through many links from past 72 hours. Help me out,
I have website and app, while signup i am sending a mail from which they will verify their account. In website is working well but, while i tired to work it with app it not happening to me. In mu AndroidManifest.xml file i have written the intent:filter with all preference, plugin, .. but
<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="xyz.com" android:path="/verifyemail/*" android:scheme="http" />
</intent-filter>
here xyz is sample. My question is,
clicking on the verify link from mail i am getting the link as follows:
www.xyz.com/verifymail/abc
here instead of abc it may be somethind else that means the various email id. How to append those and ask for the app / browser using ionic
In AndroidManifest.xml, you just need to add the following:
<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="xyz.com" android:path="/verifyemail/*" android:scheme="http" />
</intent-filter>
As i know we can't get dynamic link directly as the path has to be changed from abc to some other which is not possible. So, as you have to make it static and try another process to those functionality and you can able to traverse based on requirement.
If you're writing a cross-platform Ionic app you might want to add this plugin: https://github.com/EddyVerbruggen/Custom-URL-scheme
You can then set a matching scheme for your app (say 'myapp') in your AndroidManifest.xml:
<intent-filter>
<data android:scheme="myapp"/>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
</intent-filter>
The URL myapp://www.xyz.com/verifymail/abc will then open your app. Hope this helps?

Trying to access JNDI source on Tomcat server

I have a application running on Jboss server. on Jboss it uses JNDI sources for DB connection name cc.xml & iv.xml.(jboss/server/default/deploy/ Both jndi xml are here)
Now i have to deploy the same war on Tomcat and trying to create & access the JNDI sources from tomcat. I made following changes -
Added following code to META-INF/Context.xml
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/R2">
<ResourceLink name="ivrDataSource" global="ivrDataSource" type="javax.sql.DataSource" />
<Resource
name="ivrDataSource"
type="javax.sql.DataSource"
driverClassName="net.sourceforge.jtds.jdbc.Driver"
password=""
maxIdle="2"
maxWait="5000"
username="user"
url="jdbc:jtds:sqlserver://abc:1433;DatabaseName=IVR_GUARDIAN;tds=8.0;lastupdatecount=false;socketKeepAlive=true;"
maxActive="4"/>
<ResourceLink name="ccDataSource" global="ccDataSource" type="javax.sql.DataSource" />
<Resource
name="ccDataSource"
type="javax.sql.DataSource"
driverClassName="net.sourceforge.jtds.jdbc.Driver"
password=""
maxIdle="2"
maxWait="5000"
username="web"
url="jdbc:jtds:sqlserver://xyz:1433;DatabaseName=CC_GUARDIAN;tds=8.0;lastupdatecount=false;socketKeepAlive=true;"
maxActive="4"/>
</Context>
ADDED BELOW TO WEB.XML ----
<!-- FOR TOMCAT DEPLOYMRNT -TESTING -->
<resource-ref>
<description>ccDataSource</description>
<res-ref-name>ccDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<description>ivrDataSource</description>
<res-ref-name>ivrDataSource</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
But i am getting error-
javax.naming.NameNotFoundException: Name ccDataSource,ivrDataSource is not bound in this Context.
Always worked on JBOSS so this is new to me..Missing something here.Please suggest.
You do not have to use <ResourceLink>. Try removing <ResourceLink>s.
<ResourceLink> is used to create a link to a global JNDI resource.
Please see following links for more details.
http://tomcat.apache.org/tomcat-7.0-doc/jndi-resources-howto.html
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Resource%20Links
Hope this helps.

Manual XBAP publishing

I found a method to manually publish a regular WPF Application, but i need the same instructions for a WPF Browser app instead. Here is the regular WPF App howto: http://msdn.microsoft.com/en-us/library/xc3tc5xx(VS.80).aspx . If anyone knows what changes I need to make to my mage commands to make it work for XBAP please let me know. Thanks.
I had to alter the name of the default "Application Files" folder for one of our customers who doesn't like spaces in file or folder names and this meant re-signing the xbap after the publish. Here's the msbuild script I use to automate the process:
<Target Name="PublishWebsite" DependsOnTargets="CleanWebsiteOutputPath;CleanOutputPath;CleanWebsiteReleasePath">
<!-- Compile Website -->
<MSBuild Projects=".\Some.Namespace.Web.Site\Some.Namespace.UI.Web.Site.csproj" Targets="Clean;Rebuild;" Properties="Configuration=Release" />
<!-- Copy Website files to release folder -->
<ItemGroup>
<SiteFiles Include="Some.Namespace.UI.Web.Site/**/*.*" />
</ItemGroup>
<Copy SourceFiles="#(SiteFiles)" DestinationFolder="..\rel\Website\%(RecursiveDir)" />
<!-- Remove source code and source control files from website -->
<CallTarget Targets="CleanWebsiteAfterPublish" />
<Message Text="Website Published" />
<!-- Rename "Application Files" folder and re-sign the xbap -->
<StringReplace Pattern="\." InputString="$(ApplicationVersion)" Replace="_">
<Output PropertyName="VersionUnderscored" TaskParameter="Result" />
</StringReplace>
<MSBuild Projects=".\Some.Namespace.UI.WPF\Some.Namespace.UI.WPF.csproj" Targets="Publish" Properties="Configuration=Release;" />
<Exec Command="move "..\bin\Release\app.publish\Application Files" "..\bin\Release\app.publish\ApplicationFiles"" />
<Exec Command="$(MageExe) -update ..\bin\Release\app.publish\SomeApp.xbap –AppManifest ..\bin\Release\app.publish\ApplicationFiles\SomeApp_$(VersionUnderscored)\SomeApp.exe.manifest -wpf true -cf ..\ext\Signing\SomeApp.pfx -pwd password" />
<!-- Move published files to Release directory -->
<ItemGroup>
<XbapPublishFiles Include="..\bin\Release\app.publish\**\*.*" />
</ItemGroup>
<Copy SourceFiles="#(XbapPublishFiles)" DestinationFiles="#(XbapPublishFiles->'..\rel\Website\%(RecursiveDir)%(Filename)%(Extension)')" />
<Message Text="XBAP Published" />
</Target>

How to make System.Windows.MessageBox buttons styled?

I'm using System.Windows.MessageBox in a WPF app, and for some reason its buttons are styled the Windows 2000 way - not WinXP, not Aero, not the WPF default. Just gray with basic 3d borders.
How can I make them appear with a more modern style? (doesn't really matter which one)
You can fix this with a manifest. See this article for step-by-step instructions: Why am I Getting Old Style File Dialogs and Message Boxes with WPF
Basically, you have to add an XML file called a 'manifest' to your application.
Update:
Actually, it is very easy to do this in VS2008. Go to Project Properties->Application and click the 'View UAC Settings' button. This will automatically create an application manifest file and open it. Edit this file as follows:
Just after the line:
</trustInfo>
Paste in the following dependency section:
<!-- Activate Windows Common Controls v6 usage (XP and Vista): -->
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="*"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
My complete manifest looks like this:
<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<assemblyIdentity version="1.0.0.0" name="MyApplication.app"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
<!-- UAC Manifest Options
If you want to change the Windows User Account Control level replace the
requestedExecutionLevel node with one of the following.
<requestedExecutionLevel level="asInvoker" uiAccess="false" />
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
<requestedExecutionLevel level="highestAvailable" uiAccess="false" />
If you want to utilize File and Registry Virtualization for backward
compatibility then delete the requestedExecutionLevel node.
-->
<requestedExecutionLevel level="asInvoker" uiAccess="false" />
</requestedPrivileges>
</security>
</trustInfo>
<!-- Activate Windows Common Controls v6 usage (XP, Vista, Win 7) to support themed dialogs: -->
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="*"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</asmv1:assembly>
After doing this, just build your app, run, and voila, the MessageBox dialog buttons take on the system theme style.

Resources