Open eCard Development Center: Issueshttps://dev.openecard.org/https://dev.openecard.org/favicon.ico?16330801422013-05-15T09:49:47ZOpen eCard Development Center
Redmine Open eCard - Bug #232 (Closed): Implement read and update record command apdushttps://dev.openecard.org/issues/2322013-05-15T09:49:47ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>These apdus are needed to read and update EF.Verweis on the german health card for example.</p> Open eCard - Bug #231 (Closed): Provide FileDialog support for Androidhttps://dev.openecard.org/issues/2312013-05-14T08:47:26ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>On Android the FileDialog-Interface is not implemented.</p> Open eCard - Bug #230 (Closed): Provide full MessageDialog support for Androidhttps://dev.openecard.org/issues/2302013-05-07T09:50:06ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>On Android the MessageDialog is only capable of showing a simple message without input options.<br />Furthermore, it must be clarified how the result is returned, because we can not block and wait for it.</p> Open eCard - Bug #227 (Closed): MessageDialog not working on Androidhttps://dev.openecard.org/issues/2272013-04-24T11:25:39ZDirk Petrautzkipetrautzki@hs-coburg.deOpen eCard - Bug #226 (Closed): Android App starting problemshttps://dev.openecard.org/issues/2262013-04-24T11:25:23ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>On certain circumstances the Android App hangs on startup if a usb reader is attached.<br />Libusb is waiting for incoming device descriptors on the unix socket, but never gets one.</p> Open eCard - Bug #225 (Closed): Support for legacy activation on Androidhttps://dev.openecard.org/issues/2252013-04-24T11:23:03ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>When using the legacy activation (via the plugin for the android firefox) we redirect to the refresh address immediately after starting the paos communication.<br />Currently this causes the Adndroid app to close completely.</p> Open eCard - Bug #222 (Closed): Richclient build fails on Windows when maven-jarsigner-plugin is ...https://dev.openecard.org/issues/2222013-04-18T11:43:20ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>If the maven-jarsigner-plugin is activated in the pom.xml the richclient build fails.<br />See attached text file for debug output.</p> Open eCard - Bug #218 (Closed): Android client build fails on Windows when proguard is enabledhttps://dev.openecard.org/issues/2182013-04-11T09:09:50ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>When proguard is enabled building the Android client fails because the command line used to execute proguard is too long for Windows systems.</p>
<p>Shortened output: <br />[INFO] C:\Program Files\Java\jdk1.7.0_02\jre\bin\java [-Xmx512M, -jar, C:\Program Files (x86)\Android\android-sdk\tools\proguard\lib\proguard.jar, @proguard.cfg, -injars, 'C:\Users\Dirk\git\ecard-client\clients\android\target\classes', -injars, C:\Users\Dirk\.m2\repository\org\openecard\common\1.1.0-SNAPSHOT\common-1.1.0-SNAPSHOT.jar(!META-INF/maven/**,!META-INF/MANIFEST.MF), .......<br />[INFO] Die Befehlszeile ist zu lang.</p>
<p>Maximum length for command lines on Windows systems (XP and higher) is 8191 characters but the generated command line is about 500 characters longer.</p> Open eCard - Bug #189 (Closed): Repeatedly performing the authentication process with usb readers...https://dev.openecard.org/issues/1892013-03-21T12:33:41ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>After the authentication process has been completed, it is not possible to perform another authentication because the wrong Activity will be on top of the Activity stack and therefore the App hangs on startup. We need to ensure that the DeviceOpenActivity will be on top of the stack.</p> Open eCard - Feature #188 (Closed): Write a Log to the internal storage / sd card in the Android Apphttps://dev.openecard.org/issues/1882013-03-20T13:09:20ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>The user should be given the opportunity to enable or disable in the settings if a log is written to the internal storage / sd card.</p> Open eCard - Bug #187 (Closed): AndroidMarshaller throws an Exception when confronted with comple...https://dev.openecard.org/issues/1872013-03-20T13:00:05ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>Currently we're including a trimmed down version of the eGK cif that is fully compatible with the AndroidMarshaller.<br />However if replaced with the full eGK cif, to get access to all available DIDs for example, the AndroidMarshaller throws an Exception.</p> Open eCard - Bug #186 (Closed): Group of radio buttons not working as expected under Androidhttps://dev.openecard.org/issues/1862013-03-18T14:34:57ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>It is currently possible to select more than one radio button under Android.<br />This can be seen in the InsertCardDialog when more than one matching card is available.</p> Open eCard - Bug #170 (Closed): Wrong Error Dialog in Android Apphttps://dev.openecard.org/issues/1702013-02-06T08:15:04ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>When there is an error in the PAOS communication with the eID-Server the Android App shows the extended Length error.<br />The extended Length error dialog should only be displayed when the error actually was the extended length problem. <br />Otherwise there should be a dialog stating the real error and may give the possibility to save (and send) a log.</p> Open eCard - Bug #169 (Closed): Wrong 'More Info' URL in the Android Apps ext. Length Error Messagehttps://dev.openecard.org/issues/1692013-02-06T08:10:28ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>The URLs in The Android Apps extended Length Error Message are wrong and lead to a 404 HTTP Error. <br />The right URLS are:<br /><a class="external" href="https://www.openecard.org/de/framework/extendedlength">https://www.openecard.org/de/framework/extendedlength</a> (german)<br /><a class="external" href="https://www.openecard.org/en/framework/extendedlength">https://www.openecard.org/en/framework/extendedlength</a> (english)</p> Open eCard - Feature #151 (Rejected): Implement GUI Stepshttps://dev.openecard.org/issues/1512012-10-25T14:00:18ZDirk Petrautzkipetrautzki@hs-coburg.deOpen eCard - Feature #150 (Rejected): Implement new Designhttps://dev.openecard.org/issues/1502012-10-25T13:58:52ZDirk Petrautzkipetrautzki@hs-coburg.deOpen eCard - Bug #119 (Closed): Preinstallation of pcsc-daemon and drivers neededhttps://dev.openecard.org/issues/1192012-07-19T11:18:43ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>Currently the pcsc-daemon and drivers need to be on the device before installing the apk. A solution is needed where everything needed is shipped withing the apk to get a '1-click-install' experience.</p> Open eCard - Bug #114 (Closed): Starting the open eCard App via Intent not working on ASUS transf...https://dev.openecard.org/issues/1142012-07-16T14:26:13ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>Currently we are starting the open eCard App via a Intent which the browser sends when the users clicks the localhost-link containing the TCTokenURL. This is not working on the ASUS transformer tablet. The browser tries to open the link normally. <br />A solution could be to start a service at bootup that listens on localhost:24727</p> Open eCard - Bug #112 (Closed): Android: turning a device into landscape mode destroys stephttps://dev.openecard.org/issues/1122012-07-12T11:57:11ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>When turning a device into landscape mode the currently displayed step is destroyed. Only a white screen and the next, back, abort buttons stay.</p> Open eCard - Bug #111 (Closed): Required Checkboxes will get enabled when using the back Buttonhttps://dev.openecard.org/issues/1112012-07-10T08:26:56ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>When you go back from the pin dialog to the CHAT dialog the required checkboxes, which should be disabled, become enabled.</p> Open eCard - Bug #109 (Closed): Back Button in Android not workinghttps://dev.openecard.org/issues/1092012-07-06T11:55:39ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>The back button is not working. Activity begins to hang.</p> Open eCard - Bug #107 (Closed): missing translations for CHAT special functionshttps://dev.openecard.org/issues/1072012-07-05T08:55:10ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>translations for CHAT special functions (restricted identification, age verification) are missing</p> Open eCard - Feature #106 (Closed): Check the requested and optional CHAT against the certificate...https://dev.openecard.org/issues/1062012-07-05T07:45:19ZDirk Petrautzkipetrautzki@hs-coburg.de
<p>Currently an eID server could send a requested and optional CHAT with data groups/special functions set, for which it's certificate doesn't have the appropriate rights.<br />A check should be implemented and a security error (requested) or a disabling of optional data group should be done.</p>