Bug from Facebook in iOS app

When you add Facebook login/share/post..... in your iOS app. It's easy to integrate to your app if the app is simple. If the app is customized with custom navigation bar, you will get this error every time Facebook needs to popup VC then crashes.

 *** Assertion failure in -[UICGColor encodeWithCoder:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/UIKit_Sim/UIKit-3512.60.7/UIColor.m:1457

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Only RGBA or White color spaces are supported in this situation.'

This is an error from facebook because they cannot work with customized navigation bar. To fix this. You need to find where navigationbar is colored with image, for example:

[[UINavigationBar appearance]  setBarTintColor:[UIColor colorWithPatternImage:[UIImage imageNamed:@"bg_top_pattern"]]]; 

Change to:

[[UINavigationBar appearance] setBackgroundImage:[UIImage imageNamed:@"bg_top_pattern"] forBarMetrics:UIBarMetricsDefault]; 

The error is gone!

Implement Google Analytic V3 for iOS project without using Cocoapod

----Draft----

Do đặc thù các dự án của khách hàng nên đa số chúng ta làm các dự án maintain (nâng cấp, thêm feature v.v...). Nên việc source code sử dụng những "món" quá cũ kỹ cũng làm việc maintain của các developer khó khăn hơn.

Google Library là một trong những thư viện gây ra nhiều rắc rối nhất cho việc maintain của các developer. Khó khăn hơn, iOS cũng thường xuyên update, thêm "món" mới, bỏ "món" cũ. Điển hình là việc sử dụng Cocoapod trở nên phổ biến hơn.

Cocoapod là gì?

Google Analytics V3 đang khuyến khích người dùng nhúng vào project bằng Cocoapod. Trên trang web của Google Analytics thì cũng chỉ chỉ cách thêm thư viện bằng cách chạy bằng Cocoapod. Nhưng có cách khác mà chúng ta không cần dùng cocoapod vẫn thêm thư viện vào xài ngon lành.

A. Đối với app chưa có Google Analytics

Bạn cần download về thư viện V3 của GA (downloadv3).

Giải nén ra thì thấy có rất nhiều thứ trong đó. Chỉ copy folder GoogleAnalytics/Library và libGoogleAnalyticsServices.a vào Resource của app cần dùng GA. Add folder vào project. 

GA cũng cần thêm một số thư viện của iOS (App target -> Build Phrase -> Link Binary with Libraries). Nên check lại các thư viện cần thiết để tránh bị báo lỗi.

• libGoogleAnalyticsServices.a
• AdSupport.framework
• CoreData.framework
• SystemConfiguration.framework
• libz.dylib
• libsqlite3.dylib
• libxml.dylib
• Hướng dẫn cách add dylib trong XCode 7.0

Vào file .pch để import GA

#import "GAI.h"
#import "GAIFields.h"

Nếu ko import trong file.pch thì file nào dùng GA thì import library trong file đó.

Vào AppDelegate.m để init GA tracker

// 1 -- optional [GAI sharedInstance].trackUncaughtExceptions = YES;   // 2 -- optional [[GAI sharedInstance].logger setLogLevel:kGAILogLevelVerbose];   // 3 -- optional [GAI sharedInstance].dispatchInterval = 20;   // 4 -- optional id<GAITracker> tracker = [[GAI sharedInstance] trackerWithTrackingId:@"UA-XXXXXXX-Y"];

@"UA-XXXXXXX-Y" là tracking ID của app sau khi đã đăng ký với GA.

Vào Controller cần track, paste đoạn code này vào file.h

#import "GAITrackedViewController.h"   @interface ClockViewController : GAITrackedViewController   @end

sau đó vào chỗ mà bạn cần track thêm đoạn code dùng để track

- (void)viewDidLoad { [super viewDidLoad]; self.screenName = @"Clock"; }

Vậy là xong. Bạn có thể vào GA để xem chương trình đang chạy đã được track trên GA chưa.

Advance configuration tham khảo thêm tại đây: https://www.raywenderlich.com/53459/google-analytics-ios

B. Đối với app đã dùng Google Analytic V2

SOA and Legacy Modernization

November 21, 2013

Service-enabling legacy assets and effectively managing and orchestrating services is the first step toward realizing the promise of the New Enterprise. In this webinar, Steven Camina, Sr. Product Manager at MuleSoft, will present strategies and demo solutions for getting the most out of your legacy assets and outline the steps you can take to build a solid foundation for APIs down the road

XCode UI Automation Testing Developement

Introduction

There is a problem that we meet everyday in our development process. An application has a scenario to test; In first build, this scenario already tested with Pass status. Later, in some newer builds, some functions are added or edited. These functions somehow related to the scenario we tested in the first build. So we need to re-test this scenario again to make sure our application runs smoothly. And the problem is we need to test the same scenario from build to build. It takes a lot of time to re-test a scenario, especially, it is tested manually.

Today I’ll introduce you a new technique to help us reduce a lot of time for re-testing, which is integrated in XCode: Automation UI Testing.

What is XCode UI Testing?

I’m sure that all you us already know about the concept of UI Testing. Before WWDC 2015, Xcode already has a tool included in Instruments. Instruments is a set of tool for developer to play with their apps. That tool is called: Automation.

Automation in Instruments

But the script in Automation is written based on Javascript syntax and not really familiar to mobile developer, especially iOS developer. Besides, Automation cannot help us with debugging, detail error report and cannot put all test cases in 1 file.

Automation code is written in Javascript

But XCode UI testing can solve all the problems above. Introduced in WWDC 2015, Xcode UI Testing is a brand new tool which is integrated in Xcode 7. We can take a look at a small part in Xcode UI Testing file. We can see it is more clearly, more beautiful, and more friendly to iOS developer.

Automation code is written in Swift

Core technologies include XCTest framework and Accessibility. 

• XCTest provides the framework for UI testing capabilities, integrated with Xcode. Creating and using UI testing expands upon what you know about using XCTest and creating unit tests. You create a UI test target, and you create UI test classes and UI test methods as a part of your project. You use XCTest assertions to validate that expected outcomes are true. Test is fully compatible with both Objective-C and Swift. 
• Accessibility is the core technology that allows disabled users the same rich experience for iOS and OS X that other users receive. It includes a rich set of semantic data about the UI that users can use can use to guide them through using your app. Accessibility is integrated with both UIKit and AppKit and has APIs that allow you to fine-tune behaviors and what is exposed for external use. UI testing uses that data to perform its functions.

There also be UI Recording. This is a really great feature of XCode UI Testing which help developer write automation test code without putting too much effort. Because the code which is  generated by the recording is in swift/objectiveC, the logic of UI element is unified to the development. This would make our test cases built quickly and exactly.

APIs

There are 3 APs:

1. XCUIApplication: is a proxy for app being tested. It is independent from the application because of running in a separate process.
2. XCUIElement:
• XCUIElement is a proxy for UI elements.
• Elements can be different types: buttons, cells, windows, etc.
• Elements has its own identifiers - strings generated by the accessibility system: accessibility identifiers, labels, titles etc.
3. XCUIElementQuery: XCUIElementQuery provides access to a specific element. The result of running query is a set of current UI elements visible for the accessibility system.

With these 3 APIs, coding ui automation test can emulate almost (with exceptions) end-user interaction.

XCTestAssertions

To evaluate the result, we al so have Assertions listed by category. XCTestAssertions are categorized into 5 groups. Whenever we put assertions in our automation test code, we can evaluate this is correctly functioned or not. For example, I delete an element, I want to determine whether the element is existed or not, I can put XCTestAssertion to compare value as well as existence of the element. Assertion will fail if the value is not equal and we will get the fail report and we can know exactly where the error is. How convenient it is!

Conclusion

XCode UI Testing opens to iOS and OSX developer as well as tester a new way to do automation test for iOS and OSX, easier, faster and familiar. But since it’s still a new tool for us, it still has some limitations:

• Require iOS 9+ to run tests. Not only SDK, but latest iOS must be installed on testing device/simulator.
• Require device to be configured for development and connected to trusted host running Xcode.
• Require access to accessibility features set from privacy settings.
• Running on Mac OS only: if your QA-team have no Macs (like our do) that may be a problem.
• You could test only your main app: extensions neither watch app testing is not supported.
• Can't find any documentation for the moment.
• Can't find way to test anything outside the app. Can't switch to safari, make URL request and then go back again.
• Some other limitations may happen when running UI test
• Limitation on events, we have tap(), doubleTap() but no longPress(). Instead of longPress(), we have to use an alternative way such as pressForDuration().
• Elements must be recognised by Accessibility. For some complex application, this can be more complicated.
• This also required iOS 9 and above to run test. So Testers also need a MAC to run all the test.
• Moreover, lack of documentation is another challenge that we have to deal with.

Prospects

But over all of these challenges, we have a fabulous tool to work with. 

• If possible, we can save much time on testing. 
• In the future, Instrument Automation will be removed from Instruments and Apple recommends are moving to Xcode UI Testing for all the UI Testing.
• 1 more important things is: this is a tool from Apple, so the update to newer version of iOS with new UI control will also be supported at the same time of updating. With third party, we have to wait some time for it to update after the iOS updating.

So. It’s worth for trying right now!