Tag Archives: app

IBAN Check IBAN Validation version 2.0.4 released

I’m happy to announce that a new version of IBAN Check IBAN Validation is now available on Google Play

This release focus on stability, performance improvements and Android 13 support.

IBAN Check ✔️ helps you with the tedious task of validating International Bank Account Numbers (IBAN’s for short) and BIC (SWIFT) code when making or receiving payments.

Enter your IBAN and our IBAN validation app for Android will do the rest, telling you if the IBAN is valid ✅ or not ❌. You can share the result of the IBAN validation or copy it to the clipboard for later use.

You can also validate the BIC (SWIFT) code.
The app checks whether IBAN and BIC are for the same country or not.

IBAN Check has a list of countries that have introduced IBAN. It helps the app in the validation process. This list is updated regularly.

What is IBAN?

The IBAN or International Bank Account Number, is a code that uniquely identifies a particular account at your financial institution or bank anywhere in the world . Through the IBAN is possible to identify the country, institution, branch and account.

IBANs and BICs are used throughout the European Union , European Economic Area and Switzerland. They should be used on all payments to and from these countries.

IBAN Check can verify IBAN’s supported in following countries:

• Albania
• Andorra
• Austria
• Azerbaijan
• Bahrain
• Belarus
• Belgium
• Bosnia and Herzegovina
• Brazil
• Bulgaria
• Burkina Faso
• Costa Rica
• Croatia
• Cyprus
• Czech Republic
• Denmark
• Djibouti
• Dominican Republic
• Egypt
• El Salvador
• Estonia
• Faroe Islands
• Finland
• France
• Georgia
• Germany
• Gibraltar
• Greece
• Greenland
• Guatemala
• Hungary
• Iceland
• Iraq
• Ireland
• Israel
• Italy
• Kazakhstan
• Kosovo
• Kuwait
• Latvia
• Lebanon
• Libya
• Liechtenstein
• Lithuania
• Luxembourg
• Macedonia
• Malta
• Mauritania
• Mauritius
• Monaco
• Moldova
• Montenegro
• Netherlands
• Norway
• Pakistan
• Palestinian
• Poland
• Portugal
• Romania
• San Marino
• Saudi Arabia
• Serbia
• Slovakia
• Slovenia
• Spain
• Sweden
• Switzerland
• Tunisia
• Turkey
• United Arab Emirates
• United Kingdom
• Virgin Islands
• Algeria
• Angola
• Benin
• Burundi
• Cameroon
• Cape Verde
• Iran
• Ivory Coast
• Madagascar
• Mali
• Mozambique
• Russia
• Saint Lucia
• Sao Tome And Principe
• Senegal
• Seychelles
• Sudan
• Timor-Leste
• Ukraine
• Vatican City State

Settings.canDrawOverlays() allays returns ‘false’ on Android O

1 Reply

I was updating one of my clients app, and testing it how it behaves on Android O (API 26). The app requires permissions to draw over system windows (android.permission.SYSTEM_ALERT_WINDOW). On Android 6 (API 23) and up, you are obligated to request ‘special’ permissions while the app is running.

The ‘SYSTEM_ALERT_WINDOW’ permission is a special permission that breaks the rules set by the new permission model available on Android 6 (API 23) and up. It’s request involves calling Settings.canDrawOverlays() and if it returns ‘false‘ starting ‘Settings‘ where the user can choose to grant your app the ability to draw overlays or not.

if(Build.VERSION.SDK_INT &gt;= Build.VERSION_CODES.M)
{
   // On API 23 and later ask the user to grant us permission to draw system overlay
   // windows.
   if (!Settings.canDrawOverlays(this))
   {
      Intent intent = new Intent(
             Settings.ACTION_MANAGE_OVERLAY_PERMISSION,
             Uri.parse("package:" + getPackageName()));
 
      startActivityForResult(intent, REQUEST_PERMISSION_SYSTEM_OVERLAY_RESULT);
   }
}

There is a bug with Settings.canDrawOverlays() (only) on API 26 where it will always return ‘false’ disregarding the actual user decision. The workaround provided here is a bit ugly, but does not involves restarting the app (which will be quite annoying for the user) after the permission is granted.

The code below first checks the result of System.canDrawOverlays() if it returns ‘true’ it continues with the rest of the application flow. If it returns ‘false’ a check if we are running on Android O (API 26) is performed. If that’s the case, we are calling our ‘workaround’ method.

The ‘workaround’ method tries to add an invisible overlay window on the screen, and if that’s OK we assume that we have a permission to draw overlays, else an exception is thrown.

@Override
    protected void onActivityResult(int requestCode, int resultCode, Intent data)
    {
        super.onActivityResult(requestCode, resultCode, data);
 
        if(Build.VERSION.SDK_INT &lt; Build.VERSION_CODES.M) return; if(requestCode == REQUEST_PERMISSION_SYSTEM_OVERLAY_RESULT) { if(Settings.canDrawOverlays(this)) { m_permissionSystemOverlayWindowGranted = true; if(m_permissionReadPhoneStateGranted &amp;&amp; m_permissionProcessOutgoingCallsGranted) { startService(new Intent(this, EstatePlusService.class)); m_layoutNoPermissions.setVisibility(View.INVISIBLE); m_progressBar.setVisibility(View.INVISIBLE); m_layoutLogin.setVisibility(View.VISIBLE); } } else if(Build.VERSION.SDK_INT == Build.VERSION_CODES.O) { // NOTE: This is a workaround to fix the bug in Android O where the // Settings.canDrawOverlays() will always return 'false' if(canDrawOverlays(this)) { m_permissionSystemOverlayWindowGranted = true; if(m_permissionReadPhoneStateGranted &amp;&amp; m_permissionProcessOutgoingCallsGranted) { startService(new Intent(this, EstatePlusService.class)); m_layoutNoPermissions.setVisibility(View.INVISIBLE); m_progressBar.setVisibility(View.INVISIBLE); m_layoutLogin.setVisibility(View.VISIBLE); } } } } } /** * Workaround for Android O */ public static boolean canDrawOverlays(Context context) { try { WindowManager windowManager = (WindowManager) context.getSystemService(Context.WINDOW_SERVICE); if (windowManager == null) { return false; } final View viewToAdd = new View(context); WindowManager.LayoutParams params = new WindowManager.LayoutParams( 0, 0, android.os.Build.VERSION.SDK_INT &gt;= android.os.Build.VERSION_CODES.O ?
                                    WindowManager.LayoutParams.TYPE_APPLICATION_OVERLAY : WindowManager.LayoutParams.TYPE_SYSTEM_ALERT,
                            WindowManager.LayoutParams.FLAG_NOT_TOUCHABLE | WindowManager.LayoutParams.FLAG_NOT_FOCUSABLE, PixelFormat.TRANSPARENT);
            viewToAdd.setLayoutParams(params);
            windowManager.addView(viewToAdd, params);
            windowManager.removeView(viewToAdd);
            return true;
        }
        catch (Exception e)
        {
            e.printStackTrace();
        }
 
        return false;
    }

@Override protected void onActivityResult(int requestCode, int resultCode, Intent data) { super.onActivityResult(requestCode, resultCode, data); if(Build.VERSION.SDK_INT < Build.VERSION_CODES.M) return; if(requestCode == REQUEST_PERMISSION_SYSTEM_OVERLAY_RESULT) { if(Settings.canDrawOverlays(this)) { m_permissionSystemOverlayWindowGranted = true; if(m_permissionReadPhoneStateGranted && m_permissionProcessOutgoingCallsGranted) { startService(new Intent(this, EstatePlusService.class)); m_layoutNoPermissions.setVisibility(View.INVISIBLE); m_progressBar.setVisibility(View.INVISIBLE); m_layoutLogin.setVisibility(View.VISIBLE); } } else if(Build.VERSION.SDK_INT == Build.VERSION_CODES.O) { // NOTE: This is a workaround to fix the bug in Android O where the // Settings.canDrawOverlays() will always return 'false' if(canDrawOverlays(this)) { m_permissionSystemOverlayWindowGranted = true; if(m_permissionReadPhoneStateGranted && m_permissionProcessOutgoingCallsGranted) { startService(new Intent(this, EstatePlusService.class)); m_layoutNoPermissions.setVisibility(View.INVISIBLE); m_progressBar.setVisibility(View.INVISIBLE); m_layoutLogin.setVisibility(View.VISIBLE); } } } } } /** * Workaround for Android O */ public static boolean canDrawOverlays(Context context) { try { WindowManager windowManager = (WindowManager) context.getSystemService(Context.WINDOW_SERVICE); if (windowManager == null) { return false; } final View viewToAdd = new View(context); WindowManager.LayoutParams params = new WindowManager.LayoutParams( 0, 0, android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.O ? WindowManager.LayoutParams.TYPE_APPLICATION_OVERLAY : WindowManager.LayoutParams.TYPE_SYSTEM_ALERT, WindowManager.LayoutParams.FLAG_NOT_TOUCHABLE | WindowManager.LayoutParams.FLAG_NOT_FOCUSABLE, PixelFormat.TRANSPARENT); viewToAdd.setLayoutParams(params); windowManager.addView(viewToAdd, params); windowManager.removeView(viewToAdd); return true; } catch (Exception e) { e.printStackTrace(); } return false; }

GSM Signal Monitor 1.5 out now!

Life of a software developer

by Vladimir Paskov

Tag Archives: app

Settings.canDrawOverlays() allays returns ‘false’ on Android O

GSM Signal Monitor 1.5 out now!